On Sat, Oct 11, 2008 at 02:07:59PM -0400, Braden McDaniel wrote:
> So what are those pitfalls? By running autoreconf, the RPM build becomes
> exposed to different versions of autoconf, automake, and libtool than
> were used by the upstream developer to create the upstream source
> package. Newer versions of these tools have the potential to introduce
> incompatibilities, breaking the RPM build.
This all seems very theoretical to me. Just because it has happened
this once is unfortunate, but you have to weigh that against the
convenience of running auto{conf,reconf} after a patch to configure.ac
which is about to go upstream anyway.
I don't mind such a guideline, but don't make it mandatory, and
emphasize that patches to configure.ac/Makefile.am should go upstream
a bit more urgently than normal.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
