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

Julien Puydt julien.puydt at laposte.net
Sun Sep 23 12:43:31 BST 2018


Hi,

Le 22/09/2018 à 13:47, Bastien ROUCARIES a écrit :
> 
> Le sam. 22 sept. 2018 à 11:36, Pirate Praveen <praveen at onenetbeyond.org 
> <mailto:praveen at onenetbeyond.org>> a écrit :
> 
>     On 8/10/18 2:58 AM, Bastien ROUCARIES wrote:
>      >
>      >     - 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 ;
>      >
>      > No
> 
>     There is already such a package,
>     https://tracker.debian.org/pkg/typescript-types
> 
>     What is the current status and how to proceed here?
> 
>     I think one source package is perfect as it is only a build dependency
>     anyway.
> 
> No because it is source included. How do you take care of version hell

I don't know exactly how to take care of version hell, but I'm not sure 
it should prevent us from trying to ship something -- or we probably 
wouldn't ship a single node-* package!

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.

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


More information about the Pkg-javascript-devel mailing list