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

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 24 6:24:50 AM IST, Julien Puydt <julien.puydt at laposte.net> wrote:
>Hi,
>
>Le 23/09/2018 à 16:44, Pirate Praveen a écrit :
>> On 9/23/18 5:13 PM, Julien Puydt wrote:
>>> What do you think of the attached script? It assumes the upstream
>>> DefinitelyTyped tree is in "DefinitelyTyped.upstream" as it's the
>layout
>>> I use for my experiment, and generates a "control" file and a bunch
>of
>>> "node-types-*.install" files.
>> 
>> Did you check node-typescript-types source? It just downloads the
>> tarballs from npm registry. I think that is a better approach (only
>ship
>> the definitions we want instead of all) and instead of creating many
>> more binary packages, a provides should be sufficient (if at all
>required).
>> 
>
>Did you see the script was detecting which packages are in Debian, and 
>only then shipped them? Here I have:
>
>jpuydt at nox:~/Debian/DefinitelyTyped$ python3 build_control.py
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>490 node-types-* generated and 4266 not considered

It'd add 490 new binary packages, which I don't think will make ftp masters happy.

Even this much is unnecessary I think. Instead of looking at a node package being in Debian as a criteria, I think we can add them only if a package actually build depend on it.

>so yes, the source tree has everything, but it's only packaging as 
>binary the necessary files...
>
>In my first mail I think proposed to ship what is really often a
>*single 
>file* within each package separately ; that sounds the least complex
>(no 
>need for fancy features in a fakeupstream, no need for a complex script
>
>to build thousands of packages...).

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.