Re: [Pkg-javascript-devel] Bug#754551: ITP: node-ms -- milliseconds conversion utility

On Mon, Aug 4, 2014 at 6:13 PM, Andrew Kelley <superjoe30@gmail.com> wrote:

On Mon, Aug 4, 2014 at 6:06 PM, Marco d'Itri <md@linux.it> wrote:

If it makes sense to bundle multiple libraries in the same package which
other packages may depend on then go for it.

I understand. Here is an example of doing exactly this: http://anonscm.debian.org/cgit/pkg-_javascript_/node-chalk.git/tree/debian/watch

However let me re-iterate that ms has 104 other modules depending on it: https://www.npmjs.org/package/ms

111 LOC is small but not trivial. I think this is not an example of a package that should be blocked.

Looking at the NEW queue, I see that I have 2 packages that are trivially small and could be bundled with the project that depends on them:

node-deflate-crc32-stream

node-crc32-stream

These packages are very small and the only thing that depends on them is node-zip-stream (which also depends on node-debug which is waiting on node-ms).

Please delete these from the NEW queue and I will bundle them with node-zip-stream.

The other packages of mine that are in there are *not* trivially small, and/or have many other packages depending on them. For these I believe the proper action is to accept the upload:

node-connect-static - so far has only groovebasin depending on it. I can bundle it with groovebasin, but it's really an independent module.

node-errno - has 27 completely unrelated modules depending on it. clearly should be separate

node-groove - contains C++ bindings to libgroove and has lots of LOC. You should be happy about this one.

node-music-library-index - separate from groovebasin because both client side code and server side code depend on it. trying to bundle this one would make it confusing or impossible to work with browserify, which groovebasin uses at build-time.

node-mv - has 30 completely unrelated modules depending on it. clearly should be separate

node-prr - node-errno and node-levelup both depend on this, both of which I am trying to get packaged up.

Please tell me what further action I can take to move this process along. I've been working hard to package up a large application with many dependencies in accordance with Debian guidelines, and now it seems that I have hit an invisible wall and it's not clear who is responsible for it or what they want from me.