OTOH, is seems more useful to point developers to the web page than to
the info manual
Ok, I won't argue.
+Suitable replacements for many such problem functions are available
+from @uref{http://www.gnu.org/software/gnulib/, Gnulib}, which aims
+to provide a centralized repository of such portability functions.
+The source files are available online,
+under various licences, mostly GNU GPL or GNU LGPL, at
+@uref{http://savannah.gnu.org/cgi-bin/viewcvs/gnulib/gnulib/lib/}.
I don't see a reason to link directly to the lib/ area. For one thing,
if people just get a random .c file from lib, it is unlikely to do
anything useful, since they will be missing the .m4.
So I suggest just linking to the Gnulib home page. Also, Gnulib isn't
just about portability, there is lots of additional functionality
provided. So maybe something like this:
Suitable replacements for many such problem functions are available from
@uref{http://www.gnu.org/software/gnulib/, Gnulib}, which aims to
provide a centralized repository of such portability functions (among
other things). The source files are available online, under various
licences, mostly GNU GPL or GNU LGPL.
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
