Tomasz Kłoczko wrote:
> Really .. instead wasting time on packaging stuff which is ~7 years old it
> would be better to use that time to fix one of those handful packages
> which are still not ac 2.71 compliant
So autoconf upstream dropped 7 years (!) of incompatible changes at us in
one single update, and you expect all packages in Fedora to instantly adapt
to this major change (disguised in a minor version number bump, because
autotools are notorious for their completely non-semantic versioning)?
I really do not understand why so many upstreams are still using autotools.
A build system that fails so badly at backwards compatibility (This is not
the first time autoconf has changed incompatibly!) is just a pain for
everybody. There are alternatives (such as CMake) that handle backwards
compatibility in a much more graceful way. (In fact, the most incompatible
CMake-related change so far was actually a change in the %cmake RPM macros
and not in upstream CMake.) But autoconf still releases breaking updates.
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
