From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/62] Python3, Packge Exlude and more (Initial ACK Please)!
Date: Thu, 22 Aug 2013 11:20:46 +0100 [thread overview]
Message-ID: <1377166846.428.50.camel@ted> (raw)
In-Reply-To: <6560539.TdGG90GaLI@helios>
On Thu, 2013-08-22 at 10:07 +0100, Paul Eggleton wrote:
> On Wednesday 21 August 2013 22:58:55 Saul Wold wrote:
> > Marko Lindqvist (3):
> > texinfo: correct dont-depend-on-help2man.patch
> > SDL2: add recipe
> > boost: fix build when PARALLEL_MAKE is not set
> >
> > Otavio Salvador (1):
> > distro_features_check.bbclass: Allow checking of required/conflicting
> > features
>
> I should have asked this earlier - why does this need to be a separate
> bbclass? The code doesn't do anything if the variables aren't set, so it can't
> be because it could have an impact on existing setups that don't set them.
FWIW I do have a worry about the shear weight of the core these days as
we're building up piles of anonymous python for example. In many ways I
therefore like the idea of having more classes which get included when
they're needed.
Cheers,
Richard
next prev parent reply other threads:[~2013-08-22 10:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 5:58 [CONSOLIDATED PULL 00/62] Python3, Packge Exlude and more (Initial ACK Please)! Saul Wold
2013-08-22 9:07 ` Paul Eggleton
2013-08-22 9:14 ` Iorga, Cristian
2013-08-22 9:55 ` Martin Jansa
2013-08-22 10:55 ` Iorga, Cristian
2013-08-22 9:58 ` Phil Blundell
2013-08-22 10:20 ` Richard Purdie [this message]
2013-08-22 12:48 ` Otavio Salvador
2013-08-22 12:51 ` Paul Eggleton
2013-08-22 17:51 ` Otavio Salvador
2013-08-22 17:39 ` Khem Raj
2013-08-22 18:03 ` Khem Raj
2013-08-22 15:44 ` Burton, Ross
2013-08-22 17:32 ` Iorga, Cristian
2013-08-22 18:25 ` Burton, Ross
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=1377166846.428.50.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@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.