Re: dh_shlibdeps problem

[Stefan Hornburg <racke@linuxia.de>]

Christian Kurz <shorty@debian.org> writes:

> On 00-12-01 Stefan Hornburg wrote:
> > Petr Cech <cech@atrey.karlin.mff.cuni.cz> writes:
> > > On Fri, Dec 01, 2000 at 12:20:13PM +0100 , Stefan Hornburg wrote:
> > > > 
> > > > How can I work around the following problem. I don't know
> > > > if a package contains shared libraries, but it may.
> > > 
> > > no. it should read "if it contains arch specific packages"
> > > 
> > > > If not, dpkg-gencontrol doesn't accept the build
> > > > because it sees 
> > > > 
> > > > Depends: ,courier-base
> > > > 
> > > > The control file reads:
> > > > 
> > > > Depends: ${shlib:Depends}, courier-base
> > > 
> > > if it has no binary packages so why put it there in the first place?
> 
> > There are scenarios where this could be useful:
> > - you don't know if shared libraries needed
> 
> How should this happen? If you build the binaries, you will normally
> notice if shared libs are necessary or not. Can you please give an
> example where you don't know it?

I'm splitting courier in various binary packages. Not all of them
will contain compiled executables. So it is error-prone to
add and remove the ${shlib:Depends} from the control file.
(In the end humans forget adding it again).
Even on my moderately fast machine Courier takes quite some
to build too.

I assume that you discussed the issue of automatically adding
dependencies as RPM does vs. the Debian method. Any pointers
are appreciated.

Keep on hacking

Bye
        Racke

-- 
LinuXia Systems && Cobolt NetServices, eCommerce and more
Shop- und Datenbanklösungen mit MiniVend, Firewalls auf Debian-Basis
http://www.linuxia.de - http://www.cobolt.net
--> Junior Officer of the MiniVend/Interchange Bug Patrol <---