On Sat, 12 Jul 2014 16:12:17 +0200 Leo Iannacone <l3on@ubuntu.com> wrote: > >> > Am I missing something, or is the working code in this package > >> > really just 111 lines? Why isn't this bundled up into something > >> > more reasonable in size for the packaging system? > >> > >> No, > >> you're right. It is really small. > >> > >> But, after discussing this in JavaScript team we ended up that it > >> is better have separated packages, instead of having a big > >> "nodejs-common" (or whatever) package, in order to properly track > >> upstream releases individually. It's not the best option for the archive or for any of the users of Debian. Tiny packages like this hurt *every* Debian user by padding the Packages file with many times the content of the package. Every user gets that hit whether they use the package or not. Worse, every user gets hit every time apt update is run - not just on the main system but in every chroot, on every mirror, on every buildd. I don't appreciate my 20 or 30 build environments getting hit every single time I run a build merely for your convenience. It's very inconvenient for everyone else but this is the only chance to complain about it. > Anyway I still prefer manage modules separately, I don't see any > reason to make a "common" package.. Because tiny packages hurt the archive and hurt all users. That's more than enough reason. > And common to what? Node.js?? Express framework (since these are all > dependencies for it)? Whatever uses it. Aggregate multiple upstreams into one source package and build one binary then ITP that. This binary then becomes a dependency of whatever needs any of the content. That way, only packages which use the code are affected. If you can't do that, embed everything needed and spin out a single binary from whichever one is the unlucky reverse dependency. That way, the only extra content is a few lines in debian/copyright. Whatever is done, aggregation is the key. > It makes no sense -at least- to me. Think of people outside your own team. Think of everyone using apt. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: PGP signature