Bug#840295: Requesting RC exception for stretch for browserified javascript
On 2016, ഒക്ടോബർ 18 12:32:40 AM IST, Emilio Pozuelo Monfort <pochu@debian.org> wrote:
>Hi Pirate,
>
>On 10/10/16 11:57, Pirate Praveen wrote:
>> package: release.debian.org
>>
>> Dear Release Team,
>>
>> As discussed with FTP masters[1], I'd like to request an RC exception
>> for browserified javascript packages already in the archive.
>
>Please correct me if I'm wrong, but I haven't seen any replies to the
>questions
>you've got. I'm not sure what I'll think when you do that, but at the
>moment
>this is a nack from me. Packages can still go into contrib if the build
>tools
>can't get ready in time for the release, and then for buster
>(stretch+1) they
>could move to main.
Sorry, I was waiting to complete jison packaging (so the discussion can move to another stage). I'll add the packages, relevant bugs, missing tools for the libraries I want exception soon.
>Another question is what build tools are we missing at this point? I
>have seen
>some mentioned in the tech-ctte thread. Mostly grunt, which is ITP
>#673727. The
>main problem there seems to be that jshint is non-free, but it seems[1]
>that it
>can be made optional. Is that not the case? Are there other blockers,
>aside from
>packaging the rdeps[2]? It'd be good to know what we are missing to get
>these
>javascript packages buildable in main, and what is blocking those from
>entering
>the archive.
jison was a blocker for libjs-handlebars, I completed packaging it. For grunt, the issue is huge number of dependencies you need to package. We are crowd funding to work full time on grunt (http://igg.me/at/debian-browserify). We completed 30+ dependencies in 3-4 days. I also think jshint can be made optional.
>Cheers,
>Emilio
>
>[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673727#56
>[2] https://wiki.debian.org/Javascript/Nodejs/Tasks/grunt
Reply to: