On വെള്ളി 02 മാർച്ച് 2018 09:57 വൈകു, Jonas Smedegaard wrote: > I generally read team policies with an implicit "...as long as it > doesn't conflict with the general Debian Policy". > > Specifically, I read the "should" in above quote as "in most cases, but > not a "must". > > We have in the Javascript team an old practice of avoiding duplicate > code: When code is same for Browsers and Nodejs, we ship the code in the > libjs-* package and have that package "Provides: " the nodejs package.
Thanks for this suggestion. I think this will solve this particular case because webpack and gitlab already depend on nodejs and I don't have to declare a nodejs dependency for libjs-three. What do you think about the case of handlebars? In that case I think a separate binary is required because the command line tool must declare a dependency on nodejs, whereas the javascript library (libjs-*), does not require it.
signature.asc
Description: OpenPGP digital signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
