Re: dh_shlibdeps problem
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.
> If not, dpkg-gencontrol doesn't accept the build
> because it sees
>
> Depends: ,courier-base
>
> The control file reads:
>
> Depends: ${shlib:Depends}, courier-base
This indeed does happen to people, such as myself, in the case of my
distributed-net package (which varies between dynamically linked and
statically linked depending on platform, and is binary-only).
Stefan, there isn't a clean way to work around this. What I eventually
did was (since the only depends I had were libc6) just added libc6,
non-versioned dependency, and removed ${shlib:Depends} altogether from
the Depends line. It's not clean and it causes dependencies where none
exist (ie, in cases when distributed-net is statically linked), but
the only other option is dynamically re-creating control for each package
in debian/rules. (Ie: this solution sucks.) Really, all solutions suck.
It'd be nice (hint, hint) if dpkg could parse around this problem.
Reply to: