FESCo Proposal for blocking older version of autoconf & automake
Toshio Kuratomi
a.badger at gmail.com
Tue May 13 15:58:10 UTC 2008
Karsten Hopp wrote:
> Jason L Tibbitts III schrieb:
>>>>>>> "KH" == Karsten Hopp <karsten at redhat.com> writes:
>>
>> KH> I'd like to see a reviewer guideline instead that new packages
>> KH> should be checked if they really need to run autofoo during the
>> KH> build and if they really require to be built with ancient autofoo.
>>
>> Could you write a draft for consideration by the packaging committee?
>> List it in http://fedoraproject.org/wiki/PackagingDrafts/DraftsTodo
>> and the committee will take a look.
>>
>> Please be sure that the draft provides sufficient information on how
>> reviewers can detect and how packagers can avoid the behavior you
>> would like to discourage.
>>
>> - J<
>>
>
> The initial version is at
> http://fedoraproject.org/wiki/PackagingDrafts/AutoConf.
>
"""
The resulting configure scripts and Makefiles might be different on
systems with a different set of installed packages and thus might lead
to unpredictable results.
"""
The buildroot will be the same across runs, therefore the results should
be predictable right?
"""
Package maintainers should work with upstream to port the scripts to
recent autoconf /automake. Sometimes this won't work due to time
constraints or due to compatibility concerns for multi-platform packages
such as p.e. Firefox, but at least an attempt should be made.
"""
How does the reviewer and package maintainer know that the scripts need
to be ported?
Should the package maintainer be moving the build scripts to newer
versions in the Fedora package?
-Toshio
More information about the fedora-devel-list
mailing list