Bug#88111: policy should not dictate implementation details

[Wichert Akkerman <wichert@cistron.nl>]

Previously Julian Gilbey wrote:
> Simply not true.  Read the source code for dpkg-buildpackage.  I'm
> objecting to this until we specify the following (growing) minimal
> interface:
> 
> debian/rules [variable=value ...] target [variable=value ...]

I highly object to complicant the interface to debian/rules. Environment
variables work fine, and are *much* easier to handle, especially if we
someday decide to replace debian/rules with something that is not a
makefile.

> debian/rules -q target
> 
> exit: 2 if target cannot be built (doesn't exist), non-2 otherwise

I still completely fail to see why that -q is needed. I can't find
any argumentation for introducint it.
 
Wichert.

-- 
   ________________________________________________________________
 / Generally uninteresting signature - ignore at your convenience  \
| wichert@cistron.nl                  http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |