Bug#651819: "pkgconfig --libs enchant" specifies unnecessary libraries

[Per Olofsson <pelle@debian.org>]

Hi Agustin,

Thanks for responding.

2011-12-20 13:15, Agustin Martin skrev:
>> $ pkg-config --libs enchant
>> -pthread -lenchant -lgmodule-2.0 -lrt -lglib-2.0
> 
> Hi, Per
> 
> Those libs seem to come from 
> 
> Requires: glib-2.0 gmodule-no-export-2.0
> 
> entry in upstream enchant.pc.in

OK.

> 
>> It appears that enchant can be used without explicitly depending on
>> the extra libraries. Please consider moving them to Libs.private in
>> enchant.pc.
> 
> I guess you mean that lyx can use enchant without explicitly depending on
> above libraries, enchant itself seems to heavily rely on glib-2.0.

Yes, that's exactly what I mean. While enchant itself relies on glib,
the API it exposes doesn't require glib. So programs like lyx, which
uses the enchant API but not glib, doesn't need to link directly with
glib. This reduces the number of dependencies for lyx, which makes
various transitions (ABI, testing) easier.

> I am not familiar with pkg-config and friends. Should something like
> Requires.private help here? Or is better Libs.private as you suggest?

Yes, Requires.private would help. Not Libs.private, of course, sorry.

So, what I'm suggesting is to move glib and gmodule to a
Requires.private line.

-- 
Pelle