[Python-apps-team] Bug#638720: Odoo packaging

Dmitry Smirnov onlyjob at debian.org
Fri Apr 17 08:02:19 UTC 2015

On Fri, 17 Apr 2015 17:44:47 Ben Finney wrote:
> Yes, Debian Policy §4.13 says Debian packages should not install these
> “convenience copies” of third-party code. The third-party code should
> instead be installed by a separate Debian package made from the source
> for that code, and dependent packages should use it only from that
> package.

This is best to be determined on case-to-case basis. Often it is not feasible 
to package some rarely used code when it will not be used outside of a 
particular package. In such case installing private copy is the right thing to 
do, provided that such cases are properly documented.

Remember that every package creates a maintenance overhead. Besides often 
bundled software is not ready to be exposed system-wide.

Having said that I agree with you that we have to compartmentalise 3rd party 
components to corresponding packages when possible. We can continue doing that 
even after when Odoo is uploaded.

Also please remember that bundled javascript libraries sometimes can not be 
externalised because of incompatibilities between versions when a particular 
version must be used. This is severely complicates backporting so sometimes we 
are just using bundled library (or its copy in "missing-sources").

All the best,
 Dmitry Smirnov.


I am easily satisfied with the very best.
        -- Winston Churchill
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20150417/94f84b11/attachment.sig>

More information about the Python-apps-team mailing list