[Pkg-javascript-devel] Shipping DefinitelyTyped definitions : one binary package per definition?

[Julien Puydt]

Hi,

Le 09/08/2018 à 09:19, Julien Puydt a écrit :
> Le 08/08/2018 à 23:35, Julien Puydt a écrit :
>> I'm not convinced it's the best way to handle the situation, but here 
>> is a simple script I wrote to toy with the idea...
>>
>> (my checkout of upstream DefinitelyTyped is in /tmp, so you might want 
>> to adapt the script to your own situation)
> 
> Another toy script, this time in Python, and smarter since it creates 
> only packages for what we clearly have in Debian (the test is rough!).
> 
> (The final control file is 4k lines instead of 42k for the naive js 
> version)
>

No comment, still toying around ; another Python script, this time a 
single binary package is built, but for each node-foo in Debian where 
DefinitelyTyped has foo, a virtual node-types-foo is provided.

That looks quite neat, in fact :

- just one node-types-definitelytyped real package would provide all 
necessary node-types-foo ones, so if a package needs the @types/foo, it 
can depend on node-types-foo and the right one is pulled in ;

- when foo upstream includes the type declarations, then node-foo will 
be able to also provide node-types-foo itself, and later on when 
DefinitelyTyped stops shipping it, the newer node-types-definitelytyped 
won't provide node-types-foo anymore so the transition will be quite smooth.

What are your opinions?

jpuydt on irc.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.py
Type: text/x-python
Size: 1659 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20180809/068bff34/attachment.py>