Bug#658084: libav-extra: Really necessary?

Andres Mejia amejia004 at gmail.com
Mon Mar 19 02:59:28 UTC 2012


Here is what I propose in order to provide the lib*extra* packages
from the libav source package. [1] It essentially has libav building
the extra packages, thus no longer having to rely on a seperate source
package. This change ensures the regular and the extra packages are
built for all 'flavors' to be built depending on the architecture.

As I said before, as far as building the GPLv3 enabled libraries,
there is no reason to do that with a seperate source package. Building
them separately would not change the fact that the packages are
ultimately distributed through Debian main. The source package will
remain LGPLv2.1+. The binaries will be GPLv2+ for the regular
packages, and GPLv3+ for the extra packages.

Though the build time is increased for libav, ultimately, this change
would be better as the buildd network would not have to cope with
building from two source packages (i.e. setting up and tearing down
for libav and libav-extra for each architecture). Also, in my opinion,
it is easier and less error prone to maintain a single libav package
rather than two of them.

1. http://anonscm.debian.org/gitweb/?p=pkg-multimedia/libav.git;a=commitdiff;h=3037cab27717de75a73c77a553ab6dfad04a57da;hp=d78d2e6d0d0f43a6203ee6b78a8c0fefcab7838a

-- 
~ Andres





More information about the pkg-multimedia-maintainers mailing list