Re: Bug#754551: ITP: node-ms -- milliseconds conversion utility
On Sat, Jul 12, 2014 at 12:55:02PM +0200, Leo Iannacone wrote:
> On 12 July 2014 12:35, Steve McIntyre <steve@einval.com> wrote:
> > l3on@ubuntu.com wrote:
> >>Package: wnpp
> >>Severity: wishlist
> >>Owner: Leo Iannacone <l3on@ubuntu.com>
> >>X-Debbugs-CC: debian-devel@lists.debian.org
> >>
> >>* Package name : node-ms
> >> Version : 0.6.2
> >> Upstream Author : Guillermo Rauch <rauchg@gmail.com>
> >>* URL : https://github.com/guille/ms.js
> >>* License : Expat
> >> Programming Lang: JavaScript
> >> Description : milliseconds conversion utility - Node.js module
> >> This module provides a tiny milliseconds conversion utility able to
> >> transorm a string with a valid time unit to the equivalent number
> >> of milliseconds and vice versa.
> >> .
> >> Node.js is an event-based server-side JavaScript engine.
> >>
> >> .
> >> Node.js is an event-based server-side JavaScript engine.
> >
> > I've seen ITPs for a massive set of tiny-looking node libraries go
> > past on -devel in the last few months, so I thought it was about time
> > I looked at one. I'm a bit worried by what I've seen, considering
> > typical discussions in the past about really small packages.
> >
> > tack:~/debian/ms.js$ ls -al
> > total 52
> > drwxr-xr-x 4 steve users 4096 Jul 12 11:29 ./
> > drwxr-xr-x 112 steve users 4096 Jul 12 11:29 ../
> > drwxr-xr-x 8 steve users 4096 Jul 12 11:29 .git/
> > -rw-r--r-- 1 steve users 13 Jul 12 11:29 .gitignore
> > -rw-r--r-- 1 steve users 53 Jul 12 11:29 .npmignore
> > -rw-r--r-- 1 steve users 1026 Jul 12 11:29 History.md
> > -rw-r--r-- 1 steve users 1097 Jul 12 11:29 LICENSE
> > -rw-r--r-- 1 steve users 110 Jul 12 11:29 Makefile
> > -rw-r--r-- 1 steve users 814 Jul 12 11:29 README.md
> > -rw-r--r-- 1 steve users 223 Jul 12 11:29 component.json
> > -rw-r--r-- 1 steve users 2025 Jul 12 11:29 index.js
> > -rw-r--r-- 1 steve users 360 Jul 12 11:29 package.json
> > drwxr-xr-x 2 steve users 4096 Jul 12 11:29 test/
> >
> > tack:~/debian/ms.js$ wc -l index.js
> > 111 index.js
> >
> > 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.
How much do you think it will change in the foreseeable future? If
there are frequent changes to those 111 lines, I am buying your
argument, but if we are talking about 1-2 updates a year, a js-bundle
package (which itself could be updated every couple of weeks unless
major bugs or security issues pop up) might be more worthwhile.
Michael
Reply to: