On Sun, Jul 03, 2011 at 11:45:09AM -0400, Tom Lane wrote: > FWIW, I used to run autoconf during the builds of both the postgresql > and mysql packages for many years. That eventually became unnecessary > in both cases, but I don't recall that autoconf changes ever caused me > any trouble. (gcc, on the other hand, ...) We've been bitten with very old versions of autoconf (hello, RHEL 5). In those cases we've had to patch the generated files instead of the autoconf input files. It's a pain in the derriere doing this. However this is not a reason not to rerun autoconf. If rerunning autoconf is going to fail, then it will fail early and obviously. This problem isn't likely to affect Fedora because Fedora usually has the latest autotools. Packagers should use their discretion (as in many other cases). Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
