From: Patrick Ohly <patrick.ohly@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] Add opengl to REQUIRED_DISTRO_FEATURES for some recipes
Date: Thu, 05 Jan 2017 08:32:43 +0100 [thread overview]
Message-ID: <1483601563.28169.69.camel@intel.com> (raw)
In-Reply-To: <CAJTo0LYepu3mAAc=Y76RxBW20w1gEVH1+ms7gpfmSTB-ePfrcQ@mail.gmail.com>
On Wed, 2017-01-04 at 23:49 +0000, Burton, Ross wrote:
>
> On 4 January 2017 at 22:57, Christopher Larson <kergoth@gmail.com>
> wrote:
> These aren't buildable without it, and adding it fixes oe-core
> world builds
> with nodistro (which does not have the opengl feature by
> default).
>
>
> Am I still the only person who thinks skipping of recipes should be
> recursive, so if say libx11 throws a SkipRecipe then everything else
> that depends on it is also magically skipped?
Not at all, I'd also prefer that. If recipe "foo" has some obscure
conditions when it can be built, then repeating those conditions in any
recipe depending on "foo" is a maintenance headache.
Last time I brought this up, it was mentioned as advantage of the
current approach that conditions are explicit and thus less surprising.
There's some truth to that, but I don't believe that it outweighs the
disadvantages.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-01-05 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 22:57 [PATCH 0/6] Add opengl to REQUIRED_DISTRO_FEATURES for some recipes Christopher Larson
2017-01-04 22:57 ` [PATCH 1/6] waffle: add opengl to REQUIRED_DISTRO_FEATURES Christopher Larson
2017-01-04 22:57 ` [PATCH 2/6] piglit: " Christopher Larson
2017-01-04 22:57 ` [PATCH 3/6] libglu: " Christopher Larson
2017-01-04 23:34 ` Phil Blundell
2017-01-04 22:57 ` [PATCH 4/6] eglinfo-x11: " Christopher Larson
2017-01-04 22:57 ` [PATCH 5/6] packagegroup-self-hosted: " Christopher Larson
2017-01-04 22:57 ` [PATCH 6/6] packagegroup-core-lsb: " Christopher Larson
2017-01-04 23:49 ` [PATCH 0/6] Add opengl to REQUIRED_DISTRO_FEATURES for some recipes Burton, Ross
2017-01-05 0:52 ` Khem Raj
2017-01-05 1:13 ` Christopher Larson
2017-01-05 1:27 ` Khem Raj
2017-01-05 7:32 ` Patrick Ohly [this message]
2017-01-05 8:51 ` Richard Purdie
2017-01-05 10:35 ` Patrick Ohly
2017-01-05 8:54 ` Richard Purdie
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=1483601563.28169.69.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox