Bug#622931: libav: pkg-config files implies possible static linkage

[Neil Williams]

On Sun, 17 Apr 2011 19:51:12 +0200
Carl Fürstenberg <azatoth at gmail.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
AFAICT.

> 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. 

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20110417/6cbf5ca9/attachment-0001.pgp>