Re: Bug#622931: libav: pkg-config files implies possible static linkage
retitle 622931 Possibility to express linking modes
reassign 622931 pkg-config
Neil, thank you very much for your insightful summary of the matter. Now
it seems pretty clear that this issue cannot be handled in the libav
package, but needs to be solved at the pkg-config level. I'm therefore
reassigning this bug to pkg-config.
Full context follows:
On Sun, Apr 17, 2011 at 20:27:03 (CEST), Neil Williams wrote:
> On Sun, 17 Apr 2011 19:51:12 +0200
> Carl Fürstenberg <email@example.com> wrote:
>> It seems I've missunderstod some aspects of the features of pkg-config.
>> I assumed as there are Requires.private and Libs.private, that there was
>> some way to specify that static linkage was not possible at all.
> You mean other than letting the defaults just happen and document in
> the package that the defaults simply won't work? There's no such method
>> Perhaps an bug on pkg-config should be open to add option to prohibit
>> static linkage.
> There's nothing in pkg-config to say that dynamic linking for any one
> package will always work, why should static be any different? (e.g.
> pkg-config will continue to report data which relates to versions of
> packages which no longer exist simply because the original package
> hasn't been updated. Yes, in Debian that will cause a FTBFS but that's
> nothing to do with pkg-config.)
> pkg-config is just config, it is not a pkg checker. Checking that what
> you get actually works has to come down to the actual package. Even
> then, unless that config is supported, it will (and must be allowed
> to) just fail to build.
Reinhard Tartler, KeyID 945348A4