On Mon, Mar 16 2009, Raphael Hertzog wrote:
> On Mon, 16 Mar 2009, Manoj Srivastava wrote:
>> In the non-snippet method proposed, there is no way for the
>> package maintainer to override project defaults yet cater user set
>> variable settings, since the information is lost.
>
> You're not trying very hard to look from both sides: whether the default
> value comes from the environment or from an included Makefile, in both
> cases the user can override it with command-line arguments.
>
> Granted it means that dpkg-buildpackage would have to pass user-overriden
> flags on the command line instead of using the environment, but that can
> be done if people really want this possibility.
>
> So the policy would mandate a set of variables that could be communicated
> either via the environment or via the command-line depending on how
> authoritative the user wants to be.
>
> That would be fine for me too.
That still fails on two points:
a) Not using dpkg would mean different build environments
b) there is no way for a site or buildd admin to provide site wide
defaults that override dpkg ones but the user can override
Also, a dding new project wide builkd defaults is tied to dpkg
development and releases (which is not really a great idea either
manoj
--
"...a most excellent barbarian ... Genghis Kahn!" _Bill And Ted's
Excellent Adventure_
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
