[Rpm-maint] better way to port packages to new architectures

Kamil Dudka kdudka at redhat.com
Fri Apr 5 13:06:23 UTC 2013

Hi RPM hackers,

Dennis Gilmore routed me to this mailing-list with my question.  In order to 
fix the following bugs:


... I asked upstream to use autoconf-2.69+ for making the tarballs from now
on and got an interesting answer:


The problem is that the recommended solution (asking upstream to use a newer 
autoconf) is a one-shot solution.  It needs to be done per each single package 
and it will need to be done again when we decide to support yet another 

Running autoreconf during build (the 2nd recommended solution) is error-prone.  
It can easily pull in bugs that do not exist in the upstream tarballs, which 
themselves are extensively tested before they are declared stable.  You can 
take the following bug as an example:


Gentoo maintains a simple package sys-devel/gnuconfig that contains only 
config.{sub,guess}, which are used to replace the files provided in the 
upstream tarballs by their build system.

Could you please consider using a similar approach for RPM?

Thanks in advance!


More information about the Rpm-maint mailing list