From: Peter Seebach <peter.seebach@windriver.com>
To: "openembedded-core@"
<lists.openembedded.org.openembedded-core@lists.openembedded.org>
Subject: RFC: FOO_subtract, the logical antidote to FOO_append.
Date: Tue, 15 May 2012 14:01:10 -0500 [thread overview]
Message-ID: <20120515140110.2ba5a1be@wrlaptop> (raw)
There's a few cases where something is a huge list of space-separated
things, and it is desireable to remove one. The example currently
afflicting me is DISTRO_FEATURES_LIBC_DEFAULT; I want to end up with
the distro features including all but one of the words in it.
It seems to me that a counterpart to _append would make sense. Here
is my basic idea:
FOO_subtract = "..."
means that, when you expand FOO:
1. Fully expand it.
2. Fully expand FOO_subtract.
3. Remove any words in FOO_subtract from FOO.
4. Yield the result.
The rationale is that the semantics of things where we're using _append
seem to be consistently of the form "this is a space-separated set",
and being able to remove things from a set would be Super Handy.
So I'm proposing the semantics for consideration, and if people like
them, I will go try to implement it in my Copious Free Time.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next reply other threads:[~2012-05-15 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 19:01 Peter Seebach [this message]
2012-05-15 20:46 ` RFC: FOO_subtract, the logical antidote to FOO_append Manuel Bessler
2012-05-16 4:35 ` Saul Wold
2012-05-16 15:07 ` Mark Hatle
2012-05-16 16:23 ` Chris Larson
2012-05-16 16:43 ` Phil Blundell
2012-05-16 16:58 ` Peter Seebach
2012-05-18 4:18 ` Chris Larson
2012-05-18 6:25 ` 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=20120515140110.2ba5a1be@wrlaptop \
--to=peter.seebach@windriver.com \
--cc=lists.openembedded.org.openembedded-core@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
/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.