On Sun, Sep 16, 2012 at 07:41:57PM +0200, Alessandro Ghedini wrote:
> On Sun, Sep 16, 2012 at 04:17:36PM +0200, gregor herrmann wrote:
> > When I extend the patch I indeed get the expected Depends for
> > liboauth0 [0]. But also:
> > 
> > dpkg-shlibdeps: warning: symbol curl_slist_free_all used by 
> > debian/liboauth0/usr/lib/x86_64-linux-gnu/liboauth.so.0.8.1 found in none 
> > of the libraries
> > dpkg-shlibdeps: warning: symbol curl_slist_append used by 
> > debian/liboauth0/usr/lib/x86_64-linux-gnu/liboauth.so.0.8.1 found in none 
> > of the libraries
> > dpkg-shlibdeps: warning: symbol curl_easy_cleanup used by 
> > debian/liboauth0/usr/lib/x86_64-linux-gnu/liboauth.so.0.8.1 found in none 
> > of the libraries
> > dpkg-shlibdeps: warning: symbol curl_easy_init used by 
> > debian/liboauth0/usr/lib/x86_64-linux-gnu/liboauth.so.0.8.1 found in none 
> > of the libraries
> > dpkg-shlibdeps: warning: symbol curl_easy_setopt used by 
> > debian/liboauth0/usr/lib/x86_64-linux-gnu/liboauth.so.0.8.1 found in none 
> > of the libraries
> > dpkg-shlibdeps: warning: symbol curl_easy_perform used by 
> > debian/liboauth0/usr/lib/x86_64-linux-gnu/liboauth.so.0.8.1 found in none 
> > of the libraries
> > 
> > So not linking to any curl lib doesn't look right ...
> 
> That could be done, as long as all the applications linking directly or
> indirectly to liboauth link to a suitable libcurl too (i.e. leaving all the
> libcurl symbols unresolved in liboauth). AFAICT this is currently not enforced
> since e.g. oauth.pc only lists libcurl as Requires.private.
> 
> Directly depending on libcurl3* packages is of no use: either the application
> links to a libcurl flavour, in which case it would already Depends on a 
> suitable
> libcurl3 package, or it doesn't and it wouldn't pick up the library even if
> installed (unless forcibly loaded e.g. via LD_LOAD_LIBRARY, but that's not a
> real solution).
> 
> Also note that libcurl3* libraries are not interchangeable, since they have
> different SONAMEs and symbols versioning (i.e. once you link against one of
> them at compile time, you have to use the same to resolve libcurl symbols at
> load time).

To wrap this up: having "Depends: ..., libcurl4-gnutls-dev | libcurl4-dev, ..."
in liboauth-dev IMO is the simplest and most effective solution to the problem
exposed (libcurl4*-dev conflicts).

Cheers

-- 
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'

Attachment: signature.asc
Description: Digital signature

Reply via email to