>> On 14458 March 1977, W. Martin Borgert wrote: >> > If I package a compiler and put y.tab.c in the package, drop >> > grammar.y in d/m-s/, would it be OK or not? >> If you come up with a good reason for it, yes. But I doubt you would >> find one here. > Let's say I need a special tool to compile it, e.g. > bison-priscus, and I don't want to package it for Debian?
Seriously, the question in this thread? Where the initial mail is the answer of the question? >> > If I don't even check that bison actually can process the file, would >> > it still be OK? >> No. >> You as the maintainer have to guarantee that the file is buildable with >> tools available in main. You can't if you don't ever check this. > IIUC, this is exactly the situation of epoch.js in > knot-resolver-module-http. I assume, it has not been build from > its original *.coffee sources, because the make tool (gulp) is > not in Debian. So the package must go into contrib? Yes, thats what contrib is for. "require stuff outside main to build or function". -- bye, Joerg
