[Pkg-javascript-devel] Remove package node-uuid? (Was: Update package node-uuid?)

[Pirate Praveen]

On 9/21/18 12:29 PM, W. Martin Borgert wrote:
> Hi,
> 
> in fact, uuid is already in Debian, even the relatively recent
> version 3.2.1, but embedded in the npm package. #895625 can just
> be closed, I assume.

It is embedded because node-uuid is not available. It should be dropped
when uuid 3.2.1 is available in the archive.

> Only the depends in node-request and the build depends in
> node-http-signature need to be changed from node-node-uuid to npm.
> Also, yarnpkg and libjs-jingle-session would need to depend on
> npm.

It is not a good idea for those packages to depend on npm for just uuid,
and moreover uuid is not exposed in usual path by npm.

> Or shall we instead remove uuid from npm and let it depend on
> node-uuid? npm is 275 times larger than node-node-uuid.

yes, once node-uuid is updated, npm can drop the embedded copy. Same for
node-request.

> Minor points:
> 
>  - node-request has the latest and freshest uuid release 3.3.2
>    included in it's source package

Because node-node-uuid is still old and since you were already on it, I
did not want to update uuid first. It was in my plan to drop the
embedded copy once you update node-uuid.

>  - npm contains uuids README.md, which should be build from its
>    source README_js.md using runmd (no ITP/RFP yet)

This should be handled by node-uuid.

>  - `require('uuid')` is deprecated and should be replaced with
>    `require('uuid/[v1|v3|v4|v5]')` in node-request

I can see it is using the correct api.
lib/multipart.js:var uuid = require('uuid/v4')

>  - who needs libjs-node-uuid? can we drop the binary package?

I think it should be dropped.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20180921/148a7d01/attachment.sig>