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

Re: Q about Build-Depends vs Build-Depends-Indep

Roman Hodek wrote:

> > Currently, my gri package has the following Build-Depends:
> > 
> > Build-Depends: debhelper, netcdfg-dev, imagemagick, gs, gs-fonts, 
> > 	tetex-bin, texinfo
> > 
> > Most of those are needed for the binary-indep target (building
> > docs) and won't be needed by porters doing only the binary-arch
> > build.
> > 
> > But the docs don't say one of the Build-Depends applies only to
> > binary-arch, so what's the use?
> Policy reworded: The packages in Build-Depends are used during
> dpkg-buildpackage -B (calls clean, build, binary-arch), and
> Build-Depends-Indep are used *only* during the remaining binary-indep,
> which normally isn't used by porters. So for porters it's sufficient
> to install the pkgs in Build-Depends, whereas the source maintainer
> (that also builds the Arch: all packages) also needs
> Build-Depends-Indep.

Great, thanks.
> > Build-Depends: debhelper, netcdfg-dev
> > Build-Depends-Indep: debhelper, netcdfg-dev, imagemagick, gs, gs-fonts, 
> > 	tetex-bin, texinfo
> I guess at least debhelper is already used in the clean and
> binary-arch targets :-) Similar, the TeX docs will probably already be
> formatted during execution of the build target. So don't move them to
> Build-depends-Indep.

No, they really get built only in binary-indep.  So according to
the above, they should be in Build-Depends-Indep:


Reply to: