On 4/13/21 12:26 PM, 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?
IMO, it's naive wishful thinking, applicable to trivial packages.
Most non-trivial packages require specific versions.
Also, in general, it's not advisable to regenerate auto*tools generated
sources at all. I am aware, this thought has become unpopular, because
the autotools have been mostly "dormant" in recent years, so people are
not used to face such problems, anymore.
In Debian it's been recommended for a long time:
https://wiki.debian.org/Autoreconf
Well, ... Debian's mistake.
It also could fail - I noticed that autoconf
2.71 has several incompatibilities with the most widely used autoconf
(2.69).
This is only the tip of the proverbial "iceberg".
autoconf > 2.69 is pretty imcompatible and bugged.
Ralf
_______________________________________________
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
