On Tue, Apr 13, 2021 at 11:26:24AM +0100, Richard W.M. Jones wrote:
Hijacking this thread originally about https://fedoraproject.org/wiki/Changes/Autoconf_271 What is the current thinking in Fedora about always running "autoreconf -i" during builds that use autotools?
I think we are likely to see the least problems for projects that created their configure.ac files using autoscan. For projects that constructed them manually or in other ways, we'll likely see some fallout. I would encourage maintainers to work towards fixing these things and contributing them back upstream. Still, we would need to provide a way to disable the autoreconf step for particular problematic packages. Some projects provide their own autotools macros and wrappers around autoreconf. For example, Xfce either provides or provided xdt-autogen as a wrapper to run autoreconf with the Xfce-specific macros and other defines available. If it's best to rerun xdt-autogen in these cases, how could we handle that in the spec file so it runs the correct 'autoreconf' command?
The cons of always autoreconfing are that it slows down builds, sometimes considerably. It also could fail - I noticed that autoconf 2.71 has several incompatibilities with the most widely used autoconf (2.69).
I think the failures will be the most frustrating part of this rather than the build time. An FAQ or something of how to fix common failures for 2.71 would be useful for contributors. Thanks, -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat, Inc. | Boston, MA | EST5EDT _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
