severity 289586 normal
thanks

On Mon, Jan 10, 2005 at 06:52:53AM +0100, Matthias Urlichs wrote:

> > The source package gnutls11 Build-Conflicts: libgnutls-dev, but an
> > already installed version of libgnutls11-dev will Provide:
> > libgnutls-dev, so building will fail. Either the Build-Conflict, the
> > Provides or both should be removed from debian/control.
> 
> The point is that if the -dev package is installed, a build will link
> with the installed libraries instead of the one I'm building (the
> package has more than one shared library).
> 
> Conflicting with -dev is better than playing linker games.

Well, I think it would be an upstream bug if the binaries created by the
gnutls11 package would link to the previously installed libraries
instead of the libraries you just compiled. Anyway, I've looked at the
build process more closely, and found that upstream does the right thing
(it uses libtool which makes sure of that), but it is dh_shlibdeps
called from debian/rules that checks the installed libraries instead of
the compiled libraries. From the dh_shlibdeps manpage:

       Suppose that your source package produces libfoo1, libfoo-dev,
       and libfooâbin binary packages. libfooâbin links against libfoo1,
       and should depend on it. In your rules file, first run
       dh_makeshlibs, then dh_shlibdeps:

               dh_makeshlibs
               dh_shlibdeps âL libfoo1 âl debian/libfoo1/usr/lib

       This will have the effect of generating automatically a shlibs
       file for libfoo1, and using that file and the libfoo1 library in
       the debian/libfoo1/usr/lib directory to calculate shared library
       dependency information.

Looking at CDBS, I guess you can set DEB_SHLIBDEPS_INCLUDE and
DEB_SHLIBDEPS_LIBRARY_package to make it do what the manpage suggests.

> Just deinstall gnutls11-dev before building a new version.
> What's the problem?

Apart from that being slightly anoying, it seems wrong to me that a package
would Build-Conflict with itself. The build environment shouldn't brake
down because of previously installed packages it doesn't Build-Depend
on in my opinion. I also don't see many other source packages
Build-Conflicting with their own -dev packages.

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <[EMAIL PROTECTED]>

Attachment: signature.asc
Description: Digital signature

Reply via email to