[Debian Bug Tracking System] > You missed the point of this section, which is about cases where > there is no single build of the package. Instead, the package is > built twice (or more) with, for example, different configure options.
Oh, I think I got the point of the section, I just don't agree. The problem with invoking build stuff from the binary target is that the binary target is run as root, whereas the build target is not. Ordinarily, you don't need to be root to build a package, so invoking the sub-targets from the build target, instead of from the binary target, makes more sense. Of course, if you don't care about the root/non-root distinction, then there is no point to having distinct 'build' and 'binary' targets at all, and it doesn't matter which one accomplishes the compile step. Perhaps you'd rather change Policy to deprecate doing anything at all in the 'build' target, and recommend that everything be done (directly or indirectly) in the 'binary' target? That would certainly simplify the world. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
signature.asc
Description: Digital signature
