On 16/11/16 13:03, Pirate Praveen wrote: > > > On 2016, നവംബർ 12 9:46:15 PM IST, Pirate Praveen <prav...@debian.org> wrote: >> We now have grunt in the archive, but the upstream philosophy of grunt >> is to force everyone to use a locally installed grunt for each project >> and not support using globally installed grunt (patches for this >> support >> was rejected upstream). >> >> We'll need to patch grunt to be able to use it for building packages in >> debian environment. >> >> http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015240.html >> >> I hope we can resolve this issue before stretch release. > > This issue of building projects with globally installed grunt is fixed by > patching grunt. > > But there are more hurdles for handlebars. > > 1. It needs packaging of babel-runtime, babel-handlers and grunt-babel. I > hope to be able to package them. > > But it also needs webpack, which I hope to work around by using > node-browserify-lite. > >> So I'd like to request exception for packages if the build system is >> using gulp or browserify, > > But if I fail to get libjs-handlebars built using node-browserify-lite and > will need to package webpack, I'd like to ask an exception for > libjs-handlebars as well, because its a case similar to grunt, needs more > than 100 dependencies packaged.
I am quite reluctant to give an exception to this. IMHO if it has to go in non-free with rdeps in contrib, that's better than not having those rdeps at all, and it can be improved to having them in main in the future when all issues are resolved. Obviously if those issues can be fixed in time for stretch, then all the better. But in order to make an informed decision, please answer these questions: Is libjs-handlebars the only package for which you are asking an exception? What is the exact issue with it? Is the only issue that you need webpack/node-browserify-lite to "browserify" (as in /bin/cat) it? Or do you also need to get it to use the packaged jison? Any other issues? Cheers, Emilio
