All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Policy of explicit disabling of package features
Date: Fri, 20 Mar 2015 09:30:40 +0000	[thread overview]
Message-ID: <1426843840.29168.68.camel@linuxfoundation.org> (raw)
In-Reply-To: <550BD52C.1040601@linux.intel.com>

On Fri, 2015-03-20 at 10:07 +0200, Tanu Kaskinen wrote:
> It seems to me that a better policy would be to always explicitly 
> disable *all* features that have external dependencies that aren't 
> listed in DEPENDS. That kind of policy should reduce these 
> non-determinism issues. Full compliance with such policy may not be 
> feasible to achieve, since it requires great care to check for new 
> optional dependencies whenever updating to new upstream versions, but I 
> hope that at least "pre-emptive" patches that add explicit feature 
> disabling will be accepted even before anyone has run into actual problems.

This is the policy, if its not in DEPENDS, it shouldn't be using it.

As you say, adherence to that policy can be tricky, its something we try
and improve over time. Where we do find issue we fix them as you've seen
from the patches. We do have better detection of these issues than we've
ever had before.

Cheers,

Richard



  reply	other threads:[~2015-03-20  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  8:07 Policy of explicit disabling of package features Tanu Kaskinen
2015-03-20  9:30 ` Richard Purdie [this message]
2015-03-20 16:47   ` Tanu Kaskinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1426843840.29168.68.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tanu.kaskinen@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.