❦ 14 octobre 2016 10:49 +0200, "W. Martin Borgert" <deba...@debian.org> :
> 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?
[...]
>> 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?
This is exactly not the situation you describe above as gulp is just a
glorified make and doesn't compile anything on its own. As I said
previously, in the case of knot-resolver-module-http, the "compile" tool
is coffeescript and sassc/ruby-sass. Both of them are in main.
I am happy you said a few posts ago that you didn't want to challenge
the line, otherwise I would have thought that your goal was just to make
the life of some maintainers miserable.
--
Writing is turning one's worst moments into money.
-- J.P. Donleavy
signature.asc
Description: PGP signature
