On Fri, Feb 16, 2001 at 02:53:52PM -0600, Steve Langasek wrote:
> On Fri, 16 Feb 2001, Jochen Voss wrote:
>
> > I have two question about Build-Depends:
>
> > (1) If I want to Build-Depend on packages A, B, C, D, E, and F. And A
> > depends on B, C, D, E, and F. Should I just mention A, because it
> > implies B to F or should I enumerate them all?
>
> Does your package need package B, or does your package just need package A,
> which needs package B?
>
> I would argue (others may disagree :) that if I'm packaging a program that
> uses libfoo directly, and the program also uses libbar which links against
> libfoo, I should Build-Depend: on both libfoo-dev and libbar-dev. That way if
> tomorrow the maintainer of libbar decides to patch her package so that it
> builds "foo-free libbar", the autobuilders will still know what to do with
> /my/ package.
That is absolutely correct, and what policy dictates on this matter.
> If, OTOH, you only need B because A is linked to it, then only A belongs in
> your Build-Depends list.
Correct.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
Debian GNU/Linux Developer, see http://people.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
