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

Jérémy Lal kapouer at melix.org
Sat May 19 08:47:57 BST 2018


2018-05-17 6:31 GMT+02:00 Pirate Praveen <praveen at onenetbeyond.org>:

>
>
> On May 17, 2018 1:32:01 AM GMT+05:30, Julien Puydt <
> julien.puydt at laposte.net> wrote:
> >Hi,
> >
> >Le 16/05/2018 à 17:45, Bastien ROUCARIES a écrit :
> >> Can I suggest in all the case something pragmatic ? Could I suggest
> >> that package providing types for node-foo should be named
> >> nodetypes-foo (without hyphen in order to avoid conflict with node
> >> package)
> >>
> >> If node-foo include type it is only needed to add "Provides:
> >> nodetypes-foo (= ${Source:Version})" in node-foo.
> >>
> >> Can someone suggest a policy file change ?
> >>
> >> The same tips could be used for libjs-foo lib BTW. I have done that
> >> for node-normalize.css for instance. It avoid small package and is
> >> ftpmaster friendly
> >
> >
> >Good idea, but the question of how to actually provide nodetypes-foo if
> >it's only available in DefinitelyTyped's big repository is still open,
> >if I don't err?
> >
> >Snark on #debian-js
>
> I think just adding it as debian/types, installing it to
> /usr/lib/nodejs/foo/types and provides nodetypes-foo.
>

This upstream discussion is asking similar questions
https://github.com/Vincit/objection.js/issues/929

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20180519/2cf2dcc2/attachment.html>


More information about the Pkg-javascript-devel mailing list