On Saturday 19 May 2018 08:08 PM, Bastien ROUCARIES wrote:
> On Thu, May 17, 2018 at 6:31 AM, Pirate Praveen
> <prav...@onenetbeyond.org> wrote:
>>
>>
>> On May 17, 2018 1:32:01 AM GMT+05:30, Julien Puydt
>> <julien.pu...@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.
>
> Please provides: nodetypes-foo (= ${source:Version})Can't this be node-types-foo? Then it follows the existing node- standard and node-types can be used to filter types packages. This also makes it easier for npm2deb, which won't require any special handling for this case (when types is a separate package). node-types will be only used for types packages, so I don't see any conflict. @types/jquery -> node-types-jquery @std/esd - node-std-esm @ava/abc -> node-ava-abc
signature.asc
Description: OpenPGP digital signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
