On Tue, Oct 22, 2019 at 10:26, Julien Puydt <[email protected]>
wrote:
Le mardi 22 octobre 2019 à 10:01 +0200, Xavier a écrit :
Le Mardi, Octobre 22, 2019 09:10 CEST, Julien Puydt <
[email protected] <mailto:[email protected]>> a
écrit:
> If you want to have ts-node, why not package it properly, with a
> RFP or
> ITP?
>
> I don't see the point into packaging those together...
It was an attempt to avoid waiting 6 or 7 months in the NEW queue
with a 50% chance of getting an acceptance or never getting an
answer
(which seems to be considered as a rejection, see node-mimelib for
example).
Well, I know the NEW queue is kind of a pain, but there's a reason why
it's there, so getting around it isn't a good solution.
I don't think that is right characterization. NEW queue is not same for
all packages, javascript packages are treated differently from other
languages. ruby packages get cleared in days or maximum weeks. Also ftp
masters want more embedding for javascript packages to reduce the
number of binary packages. They don't even allow multiple binary
packages from same source package if one of the binary is
javascript/node (for example ruby-task-list). I don't think the NEW
queue situation is healthy. It is seriously demotivating and I totally
understand wanting to avoid it.
