Brett Cundal <bcundal@cundal.net> writes: > I'm working on a package that includes a .tab.c file generated by > bison... It seems to me that this file does not need to be generated > at build time, but the upstream makefile deletes *.tab.c in the > distclean rule (Obviously this rule wasn't run before distributing, > however)... Bison-generated files are usually included in source distributions so as not to make them depend on bison (just like with "configure" and autoconf). Not including the generated file is acceptable but less customary. > So, what's wrong with this picture? Should I build-depend on bison and > generate the file in the build target, or should I modify the makefile > to not delete the generated file? I'd punt the decision upstream, requesting them to either delete the removal instruction (or move it to a maintainer-clean or similar target) -- or not distribute the .tab.c, depending on bison in turn. If you can get them to take the choice you can just adjust the build-dependency accordingly. -- Robbe
Attachment:
signature.ng
Description: PGP signature