[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dh_shlibdeps problem



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
- you use dh_perl and ${perl:Depends} and upstreams remove
  the only Perl script

After all, data processing
- should be liberal to the format of user input
- very strict in its own input

So, if dpkg tools complain over missing newlines at EOF,
empty package names in depends, empty newlines at end
of control files (with a confusing error message),
they are unnecessarily annoying.

I would tolerate this behaviour if they written in C
because of its limited string processing features,
but this applies not to Perl.

Please take this not as a rant against the developers
of these software, but more as a hint to make 
Debian packaging smoother.

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 <--- 



Reply to: