Re: [PATCH 3/4] distcc: make distccmon-gnome optional and default to off

[Paul Eggleton <paul.eggleton@linux.intel.com>]

On Tuesday 15 November 2011 15:55:38 Koen Kooi wrote:
> Op 15 nov. 2011, om 15:42 heeft Richard Purdie het volgende geschreven:
> > On Tue, 2011-11-15 at 14:59 +0100, Koen Kooi wrote:
> >> Op 15 nov. 2011, om 14:43 heeft Richard Purdie het volgende geschreven:
> >>> To put this quite simply, I think there is no good reason we
> >>> shouldn't
> >>> use the mechanism we've selected to handle this kind of problem. We
> >>> should have defaults the reflect backwards compatibility. Other than
> >>> that where is the problem other than a general objection to
> >>> PACKAGECONFIG?
> >> 
> >> It forces a choice when there is a solution where things can coexist.
> > 
> > There are multiple ways of coexisting and the configuration changing
> > based on DISTRO_FEATURES doesn't force a choice either.
> 
> It does force a choice, since you don't want to change DISTRO_FEATURES when
> distributing binaries. If changing it is safe, then it isn't a
> DISTRO_FEATURE.

It forces nothing - in fact it allows a distro to make choices.

DISTRO_FEATURES and PACKAGECONFIG are both expressions of distro policy which 
is intended to be set before binaries are produced; PACKAGECONFIG is simply on 
a per-recipe basis rather than across multiple recipes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre