To sum up, those are waiting to be review/uploaded :
git://git.debian.org/collab-maint/node-inherits.git (debian native)
git://git.debian.org/collab-maint/node-block-stream.git
git://git.debian.org/collab-maint/node-rimraf.git
git://git.debian.org/collab-maint/node-fstream.git
git://git.debian.org/collab-maint/node-tar.git

There are four modules left :
they are small and look like personal tools of the upstream author.
I try to give some reasons to let them be in npm :

proto-list
 used only in one place of npm - trivial code

read
 used to prompt from command-line - less trivial, but adhoc code for npm;
 it's hard to imagine using that lib in another project, there are more
 feature-complete projects available.

slide
 "You should use it as an example of how to write your own flow control 
utilities"
 There are better and well-documented flow control libraries.
 Slide should really never go out of npm.

which
 Small and code looks like it's been cooked for npm,
 but npm should not even use this, at least when using the nodejs debian 
package.
 It could be useful to some other projects, though,
 since it provides a well-known tool to the Node.js platform.
 For that one i have more doubts.

I welcome any comments about that.

Jérémy




_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to