Re: Dropping indirect dependencies from libgnutls-config --libs

[Tollef Fog Heen <tfheen@err.no>]

* Mike Hommey 

| On Thu, Jun 29, 2006 at 07:38:56PM +0200, Andreas Metzler <ametzler@downhill.at.eu.org> wrote:
| > Hello,
| > currently "libgnutls-config --libs"' output looks like this,
| > -L/usr/lib -lgnutls -L/usr/lib -ltasn1 -lgcrypt -lgpg-error
| > listing both direct (-lgnutls) and indirect dependencies. - Its output
| > can be used for static linking.
| > 
| > I am pondering (and have now been asked by bts) on changing this to
| > only say -lgnutls for Debian, which is enough for dynamic linking. -
| > Static linking would be broken except for
| > a) libtool using packages (.la lists the indirect dependencies)
| > or
| > b) packages using pkg-config --libs --static to get the indirect
| > dependencies[1]
| 
| I got a similar report on libxml2, which suggested the use of
| xml2-config --libs to get the direct libs and xml2-config --libs
| --static to get everything. Same semantics as pkg-config.

Is there a reason why gnutls-config and xml2-config aren't just tiny
wrappers around pkg-config for backwards compatibility?  IMO, it's
kinda silly to have each package provide its own -config script with
its own set of bugs, rather than having a shared set of bugs in
pkg-config. :-)

-- 
Tollef Fog Heen                                                        ,''`.
UNIX is user friendly, it's just picky about who its friends are      : :' :
                                                                      `. `' 
                                                                        `-