On Tue, Aug 7, 2018 at 12:43 AM Niels Thykier <ni...@thykier.net> wrote: > > Bastien ROUCARIES: > > Hi, > > > > They are a few package that FTBFS due to lack of browserify under debian [1] > > > > The most significant point is to render javadoc FTBFS due to lack of > > browserified version of pako a port of zlib to javascript. > > > > I plan to upload browserify soon but browserify is blocked by: > > * node-insert-module-globals in NEWS (prod ftpmaster) > > * node-has-object-spread not yet packaged (i plan to do it) > > * node-has-template-literals not yet packaged (i plan to do it)
Just packaged this three package > > > > Browserify (or webpack) is a static compiler for javascript. I believe > > that we must use built-using field in order to be policy compliant. > > > > I can output a list of javascript module (or file installed in the > > tree) but I lack the > > debhelper skill needed to output automatically built-using. > > > > Can somebody help me ? > > > > Bastien > > > > [1] For an approximation see > > https://lintian.debian.org/tags/source-contains-browserified-javascript.html > > that also include webpack > > > > AFAIUI, Built-Using is solely to be used for compliance with licenses > (GPL or GPL-like licenses). Are these node modules under GPL or a > GPL-like license? If not, there should be no need for Built-Using. They are some module under GPL like license not yet pacakged. But I was thinking Built-Using may be used by security team in order to trigger rebuild. Bastien > Thanks, > ~Niels
