Le dimanche 24 août 2014 à 18:49 +0200, Leo Iannacone a écrit : On 23 August 2014 21:23, Jérémy Lal <[email protected]> wrote: > > Le samedi 23 août 2014 à 16:52 +0200, Leo Iannacone a écrit : > >> On 23 August 2014 12:08, Jérémy Lal <[email protected]> wrote: > >> > I prefer the first idea from Thorsten: > >> > "time", "email", "fs" packages bundling utilities by category. > >> > > >> > Let's try to make a list of categories ? > >> > >> What about: > >> * http > >> * css > >> * html > >> * time > >> * mime > >> * mail (?) > >> * log (?) > >> * fs (?) > >> > >> All of these packages (IMHO) should be named as "node-${CATEGORY}utils", i.e.: > >> * node-httputils > To avoid the case where one upstream module gets called 'httputils', i suggest a different name scheme: nodemodules-xxxx
> > > * streams > > * async > > * module loading (amd, requirejs, ...) > > Here a wiki page to list packages and modules included: > https://wiki.debian.org/Javascript/Nodejs/CommonPackages > > Please, populate it! > > > > The problem with those bundles is that we'll never know if/when > > a module inside them isn't required any more. > > Mmm .. can't codesearch.debian.net help on this ? > Of course, but it isn't as straightforward as checking dependencies. I propose that nodemodules-time *must* list which modules it "Provides", so others packages depend on node-ms (in that example) and do *not* depend on nodemodules-time. Jérémy. _______________________________________________ Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
