Kevin Kofler <kevin.kofler@xxxxxxxxx> writes: > And in addition, I consider the concept of including generated files in > what's supposed to be a source tarball to be broken by design. A source > tarball is supposed to contain SOURCE code, not generated code. Anything > needing to be generated should be generated during the build process. That sounds more like dogmatism than practical thinking. It's common to pre-generate some of the files in a distribution tarball, just so that users aren't required to have specific tools in order to build the code (unless they want to modify the input files for those tools, of course). This is not more nor less than simplifying life for your users. The autoconf case is exactly this, really. In principle you could distribute only configure.ac and require recipients to run their own copy of autoconf in order to build. In practice it's better to ship the generated configure script too. That makes for one less build dependency and one less potential source of version-skew issues. However, anybody who has a need to adjust configure.ac is going to do so and then run autoconf locally. It doesn't seem to me to be sensible to expect Fedora packagers to do differently when they need to adjust the configure script. regards, tom lane -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
