On Sun, Nov 20, 2016 at 08:48:27AM +0100, Germano Massullo wrote:
We often deal with upstream developers that bundle libraries in
their
code, so to make a package we have to debundle them, etc.
This time, an upstream dev. asked me what he could do to make easier
the work of packagers.
In this case the software is python-netjsongraph [1] that bundles
javascript-d3 library and that is being reviewd at [2]
I think it would be nice to make a discussion even for non Python
packages, so we can elaborate a sort of vademecum that a packager
could show to upstreams when there is a collaboration between them.
I think it comes down to:
- don't bundle,
- if you have to bundle, provide an easy and unambiguous configure switch
to use the system version of the dependency,
- never, never, patch stuff in-tree.
Zbyszek