This is the mail archive of the
mailing list for the binutils project.
Re: [RFC] Update to current automake/autoconf/libtool versions.
- From: Klee Dienes <klee at apple dot com>
- To: Doug Evans <dje at transmeta dot com>
- Cc: Daniel Jacobowitz <drow at mvista dot com>,"Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>,DJ Delorie <dj at delorie dot com>,ac131313 at redhat dot com,binutils at sources dot redhat dot com,gdb-patches at sources dot redhat dot com
- Date: Thu, 5 Dec 2002 15:10:56 -0500
- Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
As long as the versions of the tools are specified by a version string
referencing an official version in README-maintainer-mode, and not by
"whatever version is on sourceware.cygnus.com", I'm happy.
In practice I can't imagine there would be a problem with versions
disappearing from the FSF site before we had upgraded to the current
version (the current autoconf repository has versions of autoconf going
back to 1996). But if that's a concern, we can always replicate
official FSF releases to a local directory and cache them there.
On Thursday, December 5, 2002, at 01:58 PM, Doug Evans wrote:
Klee Dienes writes:
I'd argue that we should:
1) Specify the versions of autoconf/automake/libtool/gettext by
reference to official tarballs from ftp.gnu.org.
This places a requirement on the maintainers of ftp.gnu.org
to not delete said tarballs until binutils has been updated.
I dont' think you or they want that kind of coupling.
Better to uncouple things and have your own tarballs.
Then you can upgrade according to your schedule, not theirs.