Re: Static linking: pkgconfig vs libtool

[Simon McVittie <smcv@debian.org>]

On Sat, 20 Nov 2010 at 21:58:56 +0100, Tollef Fog Heen wrote:
> | Upstreams are only meant to change the .pc filename when they make an
> | incompatible change to the API
> 
> This seems to be the trend, but there's nothing in pkg-config's policies
> or best practices guide that specifies this.  I'm a bit undecided on it,
> since «changing API» can be changing the name of an element of an
> obscure struct or changing the whole API around.  One of them should
> cause an API bump, one should not, or at least so I think.

OK, let me rephrase what I meant in RFC terms: when the API changes
incompatibly, upstreams MAY change the .pc filename; when the API remains
compatible, upstreams SHOULD NOT change the .pc filename. Does that sound
fair? :-)

    S