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

[Bastien ROUCARIES]

On Mon, Sep 24, 2018 at 12:24 PM Pirate Praveen
<praveen at onenetbeyond.org> wrote:
>
>
>
> On 2018, സെപ്റ്റംബർ 24 2:28:00 PM IST, Bastien ROUCARIES <roucaries.bastien at gmail.com> wrote:
> >On Mon, Sep 24, 2018 at 10:43 AM Pirate Praveen
> ><praveen at onenetbeyond.org> wrote:
> >>
> >> On 9/24/18 2:09 PM, Bastien ROUCARIES wrote:
> >> >> I think it is over engineering and making things unnecessarily
> >complex. This can be a fallback option if a separate version of type
> >definition is required instead of the centrally shipped version.
> >> > And how to you keep version in sync ?
> >>
> >> You always ship the latest in node-typescript-types package and ship
> >> separate definitions only in case something don't work. I don't think
> >we
> >> have to keep it strictly in sync with the node modules. For example,
> >we
> >> have nodejs 8.11.2 but @types/node only has 8.10.x.
> >
> >I believe it is quite fragile compared to
> >https://wiki.debian.org/Javascript/GroupSourcesTutorial
>
> I think the type definitions don't change for every js code change so its not as fragile. If it really change to breaking builds, then only we need to do the extra work of adding it to corresponding node package. Adding multiple tarballs is real pain and that has to be the last resort I think.

No it is quite easy with newer fakeupstream support. It a joy, Did you try ?

Bastien
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> --
> Pkg-javascript-devel mailing list
> Pkg-javascript-devel at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel