Ben Finney <ben+deb...@benfinney.id.au> writes: > Which of the standard ‘debian/rules’ targets need their requirements > declared in “Build-Depends” (and “Build-Depends-Indep”)?
> Policy §7.7 says: > Source packages that require certain binary packages to be installed > or absent at the time of building the package can declare > relationships to those binary packages. > This is done using the `Build-Depends', `Build-Depends-Indep', > `Build-Conflicts' and `Build-Conflicts-Indep' control fields. > What standard targets does this “at the time of building the package” > entail? The “test” target? The “get-orig-source” target? What official > set of standard targets obligate their requirements to be declared in > this field? > Note that I'm not looking for opinions about what would be a good idea; > I'm looking for how this policy section is interpreted for normative > behaviour. What's currently done everywhere in the archive is that the targets run by dpkg-buildpackage (either arch or arch-indep builds) must have their dependencies listed, and dependencies for the other targets are not listed. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87a9g11h02....@windlord.stanford.edu
