On Tuesday 18 October 2016 12:32 AM, Emilio Pozuelo Monfort 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.

I was waiting for jison packaging to complete, so the discussion can
focus on the browserify part. jison is not accepted in main. I'll reply
to those questions now.

> 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 blocking libjs-handlebars, which is now packaged. Now only
grunt is blocking. The huge number of dependencies is the only issue
with grunt. We are crowd funding to work full time for a month to get
this packaged -> http://igg.me/at/debian-browserify. We have already
completed 30+ dependencies in last 3-4 days. If we cannot complete grunt
for jessie, then only we need to consider the exception.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to