Would it be a good idea to keep in next release only node packages matching one of these conditions:
- providing a meaningful binary (not that stupid rimraf, but marked-man of course yes) - or depending on node-gyp (keep them because that's what debian nodejs addons do best, npm sucks at installing nodejs addons depending on system libs). - or having a reverse (build-)dependency, or what's the point ? - or being less than one year (approx.) behind upstream (yes i think npm or node-postgres should not be in next stable) If we don't take some action before release, users are going to be angry of the poor quality of the packages we put in stable. I have my share of responsibility in that fact, in this email is an attempt at fixing things... Thank you for considering it seriously. 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
