On Sat, 24 Jan 2015 19:42:20 +0100, Ralf Corsepius wrote: > In many other cases autoreconf can cause subtile and hard to find > issues. In complex cases, it doesn't work at all. Especially the former can be troublesome if they don't cause a build to fail. For example, it can lead to issues such as undefined/unsubstituted macros, dropped lines from Makefile*.in templates, files like config.h.in or even m4 files. Packaging guidelines that ask packagers to run autoreconf always will lead to packagers adding something to a spec file without spending extra time on carefully examining the results. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
