On Wed, 15 Feb 2006, Anthony DeRobertis wrote:
Policy 7.6 does, as quoted in my original report. A bigger excerpt reads (notice the "must be satisfied"):"The dependencies and conflicts [Build-Depends, Build-Depends-Indep, Build-Conflicts, and Build-Conflicts-Indep] must be satisfied (as defined earlier for binary packages) in order to invoke the targets in debian/rules, as follows: "Build-Depends, Build-Conflicts "The Build-Depends and Build-Conflicts fields must be satisfied when any of the following targets is invoked: build, clean, binary, binary-arch, build-arch, build-indep and binary-indep." Do you disagree that the above section of Debian Policy requires Build-Depends to be installed before invoking ./debian/rules clean?
No, I don't disagree with this. I think that wording could be chosen better though, to be less misleading. This statement does *not* mean that you cannot invoke the mentioned targets without satisfying the Build-Deps first. Policy sets standards for packaging, but it cannot and does not regulate the behaviour of the tools used to build the packages (otherwise I would have to file a grave bug against myself every time I forget to check that all the Build-Deps are installed :-). To me it's quite clear that the intended meaning of the above statements is "package must declare Build-Depends on all non-Essential packages which are used in build, clean, ... targets". I have discussed this issue with the member of release team (Steve Langasek) and he agreed with my opinion on the matter.
Best regards, Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
