On 07/13/2015 02:40 AM, Ben Finney wrote:
> Ben Finney <ben+deb...@benfinney.id.au> writes:
> Looking through the archive, I get the impression that one approach which
> could work is to collect multiple separate works by some related theme,
> and distribute some smaller number of larger, aggregate binary packages.
> Examples include the packages ‘emacs-goodies-el’ and ‘devscripts’: these
> pacakges don't go to special effort to integrate the code, they just
> bundle them together for ease of packaging and maintenance.
> them can be grouped together by some common theme, and maintained as
> aggregate Debian packages.
This is the most obvious approach. It was also discussed in the 'Small
Node.js packages in NEW' thread:
One significant downside to bundling small Node.js packages is that an
RC bug on one of the included modules threatens removal of all unrelated
reverse dependencies too.
There is also missing infrastructure to keep track of multiple upstreams
in a single package. Some wrapper around uscan with multiple watch files
and/or some server side helper will be needed for this. While it's
something I could work on, I don't have the time nor motivation for it.
Have a look at the 'OpenLayers 3' thread for all the Node.js packages
that need someone else to take care of them:
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1