From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] rm_work.bbclass: inhibit rm_work per recipe
Date: Tue, 26 Mar 2013 17:52 +0000 [thread overview]
Message-ID: <6500457.3vgtoKXQDv@helios> (raw)
In-Reply-To: <1364318752.6320.27.camel@phil-desktop.brightsign>
On Tuesday 26 March 2013 17:25:52 Phil Blundell wrote:
> This doesn't seem (at the risk of invoking an unintended metaphor)
> entirely black or white. Maybe it should just be "RM_WORK_EXCEPTIONS"
> or something.
"exception" has another meaning to my mind. I've sent out a patch to change it
to RM_WORK_EXCLUDE.
> Of course, you can get the same effect in your distro configuration by
> saying:
>
> RM_WORK = "rm_work"
> RM_WORK_pn-icu-native = ""
> INHERIT += "${RM_WORK}"
>
> so I must admit to being slightly ambivalent about whether the extra
> syntactic sugar is all that valuable.
True, that works; I think having an explicit variable makes it easier to
understand what's going on though and is a little harder to typo and have your
work removed when you didn't want it to be ;)
> And then again you can always use rm_old_work instead. :-)
I'm sure this has come up before, but is rm_old_work something we ought to
have in OE-Core?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-03-26 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 7:01 [PATCH 0/1] rm_work.bbclass: inhibit rm_work per recipe Qi.Chen
2013-03-13 7:01 ` [PATCH 1/1] " Qi.Chen
2013-03-26 17:12 ` Paul Eggleton
2013-03-26 17:15 ` Burton, Ross
2013-03-26 17:25 ` Phil Blundell
2013-03-26 17:52 ` Paul Eggleton [this message]
2013-04-09 21:01 ` Phil Blundell
2013-04-09 22:55 ` Martin Jansa
2013-03-26 17:55 ` Martin Jansa
2013-03-26 18:02 ` Paul Eggleton
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=6500457.3vgtoKXQDv@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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.