On Sat, 2 Jul 2005, Andrew Dunstan wrote:
Marc G. Fournier wrote:
On Sat, 2 Jul 2005, Peter Eisentraut wrote:
Bruce Momjian wrote:
Does the FreeBSD one actually produce different output?
If it did not, why would they bother making a separate package called
"gnu-autoconf" with the note "This port is specifically designed for
developers that want to create cross-platform software distributions on
FreeBSD."?
If it did produce different output, why haven't we noticed it prior to
this? Has there actually *been* a problem that nobody has reported?
Is autoconf actually run as part of any of our packaging scripts? My
impression was that developers ran it and the committed the results (e.g. a
configure script), unlike, say, bison where the scripts for tarballs have to
call it. But then, of course I hardly know :-)
Every time I do a release, the last step is to update teh version numbver
in configure.in and run autoconf on it, and I do that using the version of
autoconf that is on the development server itself (ie. the FreeBSD one)
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
