<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jul 12, 2014 at 3:57 AM, Frederic Peters <span dir="ltr"><<a href="mailto:fpeters@debian.org" target="_blank">fpeters@debian.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Steve McIntyre wrote:<br>
<br>
> I've seen ITPs for a massive set of tiny-looking node libraries go<br>
> past on -devel in the last few months, so I thought it was about time<br>
> I looked at one. I'm a bit worried by what I've seen, considering<br>
> typical discussions in the past about really small packages.<br></blockquote><div><br></div><div>I am largely responsible for this. However many of the ITPs I have filed I managed to avoid as (indirect) dependencies by submitting patches upstream and when appropriate, inlining the dependency. Most of the problematic ones you saw are closed now, including the 2 at the end of this email.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
><br>
> [...]<br>
><br>
> tack:~/debian/ms.js$ wc -l index.js<br>
> 111 index.js<br>
><br>
> Am I missing something, or is the working code in this package really<br>
> just 111 lines? Why isn't this bundled up into something more<br>
> reasonable in size for the packaging system?<br></blockquote><div><br></div><div>Consider my perspective for a moment here. I am trying to package groovebasin, which depends on various modules:</div><div><br></div><div>
<div>groovebasin (1.2.0) # waiting on dependencies</div><div>...many more dependencies...</div><div>├─ zip-stream (~0.3.0) # waiting for node-debug to update</div><div>│ └─ debug (~1.0.2) # l3on is waiting for node-ms in the NEW queue</div>
<div>│ └─ ms (~0.6.2) # waiting in the NEW queue...</div></div><div>...many more dependencies...</div><div><br></div><div>So now I'm waiting for node-ms in the NEW queue and people are complaining that 111 lines is too small for a code module?</div>
<div><br></div><div>What do you expect me to do? It would be very easy to just bundle all node_modules with the package but that is against Debian guidelines. Each dependency must track upstream. So that's exactly what we're doing and we're getting flak for it.</div>
<div><br></div><div>It seems that Debian wants 2 contradictory things from me at the same time.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
ITP: node-ansi-regex<br>
$ git clone <a href="https://github.com/sindresorhus/ansi-regex" target="_blank">https://github.com/sindresorhus/ansi-regex</a><br>
$ cat ansi-regex/index.js<br>
'use strict';<br>
module.exports = function () {<br>
return /\u001b\[(?:[0-9]{1,3}(?:;[0-9]{1,3})*)?[m|K]/g;<br>
};<br>
<br>
ITP: node-quotemeta<br>
$ git clone <a href="https://github.com/substack/quotemeta.git" target="_blank">https://github.com/substack/quotemeta.git</a><br>
$ cat quotemeta/index.js<br>
module.exports = function (str) {<br>
return String(str).replace(/(\W)/g, '\\$1');<br>
};<br></blockquote><div><br></div><div>These 2 are indeed stupidly small. I have managed to work around packaging these 2 modules up and closed the ITPs.</div><div><br></div><div>I have taken a lot of time to try to avoid packaging modules for Debian which could be avoided. I have done this by painstakingly getting patches merged in many upstream projects to change dependencies to better ones, or fewer ones. When I started it looked like there were about 80 packages to create, but I have brought that number down by a factor of 2.</div>
<div><br></div><div>I do not think that node-ms is stupidly small. 104 other packages depend on it in the NPM registry: <a href="https://www.npmjs.org/package/ms" target="_blank">https://www.npmjs.org/package/ms</a></div>
<div><br></div><div>
Please consider uploading node-ms and know that I am aware of the pain of small packages and I am working hard to strike the balance between properly tracking upstream and avoiding cruft.</div><div><br></div><div>Regards,</div>
<div>Andrew</div></div></div></div>