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

Re: Separating packages.

On Mon, Apr 05, 2004 at 06:11:57PM +0300, Fabian Fagerholm wrote:
> On Mon, 2004-04-05 at 14:55, n.v.t n.v.t wrote:
> > What does the ${shlibs:Depends}, ${misc:Depends} mean? I can't find the 
> > meaning of those in the debian policy either? Why not just put depends of 
> > the splited package in the depends line instead of this?
> You can manually enter the dependencies of each package, that's fine --
> but it could be a lot of work for a human. Debhelper is there to help
> you.
> ${shlibs:Depends} and ${misc:Depends} are documented in the debhelper
> documentation [0]. Basically, ${misc:Depends} tells debhelper to insert
> dependencies for packages that you need because you have used some
> debhelper feature. ${shlibs:Depends} is a debhelper program that
> generates a shlibs file for shared libraries.

Actually, ${shlibs:Depends} is implemented by dpkg-shlibdeps, in
dpkg-dev. dh_shlibdeps in debhelper is a trivial wrapper around it.

> Of course, if you don't use debhelper in your package (you should :) or
> if your package doesn't have shared libraries, then you don't need
> these.

Every package containing dynamically linked binaries should use


Colin Watson                                  [cjwatson@flatline.org.uk]

Reply to: