Re: Should build-depends only list direct dependencies?
On Tue, May 23, 2000 at 10:35:58AM +0300, Fabrizio Polacco wrote:
> On Mon, May 22, 2000 at 07:56:26AM +0300, Antti-Juhani Kaijanaho wrote:
> > On Sun, May 21, 2000 at 05:16:39PM -0400, Michael Alan Dorman wrote:
> > > If I'm building a module X, that depends on library Y, which depends
> > > in turn on library Z, am I correct in assuming that I need only
> > > specify a build-depends on library Y, and that the implicit dependency
> > > on library Z can be considered taken care of?
> >
> > It depends :-)
> >
> > This is the intention: If you directly use Z, you should build-depend
> > on it. If you need Z only because Y needs it, you should not build-depend
> > on it.
> >
> > In other words, list only those packages *you* need. What others (for
> > example the packages you build-depend on) need is their business.
>
> Humm, looks reasonable, but ... i desagree.
>
> It would be so it you are also building Y, or doing a 'make world'.
> But if to build X you need the binary packages Y and Z installed, you
> directly depend on them both, indipendently on the fact that Y, to
> build, needs binary Z installed.
X's Build-Depends: control field simply states which *binary* packages
need to be installed to build X. It says nothing about the packages
required to build those dependencies.
This is so that autobuilders or whatever can know which binary
packages must be installed to build a given package from source.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
Reply to: