❦ 13 juillet 2014 08:50 +0100, Neil Williams <codehelp@debian.org> :
>> > And I've got to ask: for the couple of trivial examples that
>> > Frederick pointed out - why on earth do these even exist as
>> > libraries instead of being inlined wherever they're needed?
>>
>> Because, in node, a library is cheap and the functionality get unit
>> tested. That's why there are so many dependencies in this ecosystem.
>
> Unit tests do not preclude inlining.
> Unit tests do not preclude aggregation.
>
> It's all just about multiple blocks of code in dedicated directories
> inside a single source package building a single binary package from
> which any other package can pick and choose the bits that package needs.
>
> Just what is wrong with one binary package putting lots of js
> in /usr/share/javascript/$library/$version/ and using symlinks in the
> bigger package to pull in the files that package wants?
Aggregation is not inlining. I was talking about inlining. I have no
opinion about aggregation.
--
/* Thanks to Rob `CmdrTaco' Malda for not influencing this code in any
* way.
*/
2.4.3 linux/net/core/netfilter.c
Attachment:
signature.asc
Description: PGP signature