[Pkg-javascript-devel] How to ship DefinitelyTyped's type definitions?

[Julien Puydt]

Hi,

Le 13/05/2018 à 21:08, Bastien ROUCARIES a écrit :
> On Sun, May 13, 2018 at 5:51 PM, Julien Puydt <julien.puydt at laposte.net> wrote:
>>
>> Le 11/05/2018 à 22:47, Bastien ROUCARIES a écrit :
>>
>>> Use dpkg-source multiple tar ball. Like node-function-bind or node-acorn
>>
>> I'm not quite sure shipping a tarball with >4000 type definitions for
>> each and every package which will need one is a good idea.
>>
>> What's wrong with a debian/README.source explaining where debian/types/*
>> files come from, and just the needed files?
> 
> I mean every package should ship types that belong to it. no big
> package and use something like
> https://raphaelhertzog.com/2010/09/07/how-to-use-multiple-upstream-tarballs-in-debian-source-packages/

I will need more explanations, sorry ; for me the situation is :
- foo1 upstream is a <100k javascript project ;
- ...
- foo4000 upstream is a <100k javascript project ;
- DefinitelyTypes' types/ directory weights 257M (du -h) and contains
the type definitions of all 4000 of the above.

There isn't a small tarball with the required type definitions for each
project : there is a big one for all of them. So adding an upstream
tarball means adding a big thing to many packages... and that doesn't
sound good.

Snark on #debian-js

PS: 4000 is an understatement:
jpuydt at nox:/tmp/DefinitelyTyped$ ls types/ | wc -l
4413
and still growing : it looks like people find it much easier to add type
definitions there than to upstream. (And that's the optimistic point of
view -- the pessimistic one is that they don't even bother contacting
upstream!)