On Mon, 17 Jun, 2013 at 15:29:39 GMT, Michael Schwendt wrote:
> One problem with that is, one cannot "blindly" run autoreconf -fi and
> expect it to be 100% compatible with the multitude of Autotools' based
> projects. Typically one will need to update the configure script, m4
> macros as well as Makefile.{am,in} templates. And if one doesn't verify
> the build framework, one can miss files where regenerating them drops
> stuff (as one example, config.h.in files where someone has inserted
> stuff the wrong way).
There are also those rare upstreams which run autoreconf once, commit
the generated files, then make "minor" changes to configure and friends
directly. Running autoreconf on these projects is bound to fail and
upstream might be unhappy moving "back" to editing the .in and .ac files
directly.
--Ben
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
