Bug#748599: Packages must not depend on libavcodec-extra-NN

[Reinhard Tartler <siretart@gmail.com>]

On Mon, May 26, 2014 at 2:04 PM, Jakub Wilk <jwilk@debian.org> wrote:
> Thanks for the bug report.
>
> * Reinhard Tartler <siretart@gmail.com>, 2014-05-18, 13:43:
>>
>> The libav package provides two flavors of libavcodec: libavcodecNN and
>> libavcodec-extra-NN, with NN being the current soname (the current
>> transition changes NN from -54 -> 55).
>>
>> It is not a good idea for packages to depend on libavcodec-extra-NN in any
>> case. Instead, packages should depend on the libavcodec-extra meta package
>> that depends on the latest libavcodec-extra-NN package.
>
>
> Well, I don't think it's a good idea to ever depend on shlib metapackage.
> That would normally be a violation of Policy §8.6:
>
> “If a package contains a binary or library which links to a shared library,
> we must ensure that, when the package is installed on the system, all of the
> libraries needed are also installed. These dependencies must be added to the
> binary package when it is built, since they may change based on which
> version of a shared library the binary or library was linked with […].”


That is correct, and I'm not arguing with that. It makes only sense
for packages that only execute avconv, and do link against directly
against libavcodec. This was the case for #748546.


-- 
regards,
    Reinhard