Re: [Pkg-dns-devel] Bug#833309: "Browserified" stuff (knot-resolver-module-http: please package embedded epoch.js separately)
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, Oct 14, 2016 at 10:49:06AM +0200, W. Martin Borgert wrote:
> On 2016-10-13 22:39, Joerg Jaspert wrote:
> > 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?
Then the build tool is not in Debian, which means that the program can be in
contrib, but not in main.
> > > 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, until the build tool is packaged (or replaced by something that is
packaged, such as cat) that is true.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----