[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoconf: small documentation obsolescences

From: Paul Eggert
Subject: Re: autoconf: small documentation obsolescences
Date: Sun, 28 Nov 2004 20:26:52 -0800
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Thanks for the bug report.  I installed this patch.  The
http://sources.redhat.com/autoconf/ URL was fixed a while back, I

2004-11-28  Paul Eggert  <address@hidden>

        Fix documentation problems reported by Russ Boylan in
        along with some nearby cruft.
        * doc/autoconf.texi (Libtool): Libtool can be used without
        Automake (not without Autoconf).
        (Introduction): Mention lists.gnu.org.
        * BUGS: Don't mention bugs.gnu.org.
        Remove mention of ancient libtool compatibility problem.
        * NEWS: Mention that bugs.gnu.org is kaput.
        * README: Likewise.  Mention where mailing list archives can be found.

Index: BUGS
RCS file: /cvsroot/autoconf/autoconf/BUGS,v
retrieving revision 1.23
diff -p -u -r1.23 BUGS
--- BUGS        26 Sep 2002 06:16:44 -0000      1.23
+++ BUGS        29 Nov 2004 04:24:32 -0000
@@ -26,24 +26,10 @@ file before using Autoconf, and especial
 Autoconf must not be used in production if there are ``Serious'' bugs,
 and use with caution an Autoconf with ``Important bugs''.
-Many other bugs are registered on the GNATS server:
-     http://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf
-Please, don't register bugs listed below: we already know we have to
-address them.
 * Status
                     | Sane for full scale use.  |
-* Interoperability bugs
-** libtool 1.4.2, configure.ac, and AC_CONFIG_AUX_DIR
-configure.ac files that use AC_CONFIG_AUX_DIR do not work with libtool
-1.4.2.  To work around the problem, you can rename configure.ac to
-configure.in.  Or you can apply Roger Leigh's patch to libtool; see
+* No known serious or important bugs.
Index: NEWS
RCS file: /cvsroot/autoconf/autoconf/NEWS,v
retrieving revision 1.330
diff -p -u -r1.330 NEWS
--- NEWS        20 Aug 2004 23:59:22 -0000      1.330
+++ NEWS        29 Nov 2004 04:24:33 -0000
@@ -348,8 +348,9 @@ Release tips:
   More of them.
-  The GNATS base has moved to
+  The GNATS base moved to
+  (It is no longer available, though.)
 ** Misc.
RCS file: /cvsroot/autoconf/autoconf/README,v
retrieving revision 1.20
diff -p -u -r1.20 README
--- README      2 Sep 2004 19:54:20 -0000       1.20
+++ README      29 Nov 2004 04:24:33 -0000
@@ -34,11 +34,12 @@ to maintain many similar sets of install
 Be sure to read BUGS (especially if this version is not an official
 release) and INSTALL.
-Mail suggestions to address@hidden, report bugs on
-http://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf or to
+Mail suggestions to address@hidden, report bugs to
 address@hidden, and submit patches to address@hidden
 Always include the Autoconf version number, which you can get by
-running `autoconf --version'.
+running `autoconf --version'.  Archives of address@hidden can be
+found in <http://lists.gnu.org/archive/html/bug-autoconf/>, and
+similarly for the other mailing lists.
Index: doc/autoconf.texi
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.844
diff -p -u -r1.844 autoconf.texi
--- doc/autoconf.texi   26 Nov 2004 18:45:53 -0000      1.844
+++ doc/autoconf.texi   29 Nov 2004 04:24:34 -0000
@@ -667,6 +667,10 @@ Summary} for details.  Patches relative 
 current @acronym{CVS} version can be sent for review to the
 @email{autoconf-patches@@gnu.org, Autoconf Patches mailing list}.
+Archives of @email{bug-autoconf@@gnu.org} can be
+found in @uref{http://lists.gnu.org/archive/html/bug-autoconf/}, and
+similarly for the other mailing lists.
 Because of its mission, Autoconf includes only a set of often-used
 macros that have already demonstrated their usefulness.  Nevertheless,
 if you wish to share your macros, or find existing ones, see the
@@ -761,7 +765,7 @@ shared libraries, linking reliably with 
 installed by the superuser, and supplying a consistent versioning system
 (so that different versions of a library can be installed or upgraded
 without breaking binary compatibility).  Although Libtool, like
-Autoconf, can be used on its own, it is most simply utilized in
+Autoconf, can be used without Automake, it is most simply utilized in
 conjunction with Automake---there, Libtool is used automatically
 whenever shared libraries are needed, and you need not know its syntax.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]