❦ 6 octobre 2016 20:47 CEST, Adrian Bunk <bunk@stusta.de> : >> > If you fancy explaining what you think browserified means w.r.t. the >> > Jison stuff, go ahead of course. That might at least help to focus the >> > discussion a bit. Just don't feel obliged to because I said so. >> >> The libjs-handlebars issue has little to share with browserified >> JS. Browserified JS is usually just concatenated JS. Here, there is an >> equivalent of flex/bison involved. That's quite unusual and is more a >> build process. If the TC rules over this issue, it should drop the >> "browserified" part. Otherwise, a negative answer would also apply to >> more basic packages. >>... > > Why is Grunt such a blocker here? I didn't mention Grunt because in this case, it is not really a problem. Whatever Grunt got packaged or not doesn't change the situation for libjs-handlebars. What this package needs is jison. Once jison is here, this package becomes buildable from tools in main and can enter in main (since there is a tolerance for pre-generated files). > If I understand it correctly, Grunt is a powerful build system that can > do a gazillion different things and has many dependencies. Yes. > For the basic browserified JS case, could a much simpler tool like > node-browserify-lite produce the same output? I can't say. -- AWAKE! FEAR! FIRE! FOES! AWAKE! FEAR! FIRE! FOES! AWAKE! AWAKE! -- J. R. R. Tolkien
Attachment:
signature.asc
Description: PGP signature