Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/2] variable/include tracking and _remove
Date: Wed, 15 Aug 2012 20:14:20 -0500	[thread overview]
Message-ID: <cover.1345079338.git.peter.seebach@windriver.com> (raw)

These aren't entirely related, but I don't think I could get
the _remove feature separated out cleanly, and there was no way
I could implement it on a tree without the variable tracking. :)

Patch #1 is a rebase/merge/cleanup of the variable and include tracking
feature I've previously sent in; this version is much cleaned up,
and produces a lot less output (<1MB instead of >10MB for a typical
project in our build system) which is substantially more informative.

Patch #2 is a proof-of-concept demonstration of how to make a _remove
keyword. Usage:

        DUMMY = "foo"
        DUMMY += "bar"
        DUMMY_remove = "foo"
        # DUMMY="bar"

This only works for space-separated lists, but we have a LOT of those.
The only obvious things I see that really are lists, and aren't
space-separated, are OVERRIDES and PATH, and I'm pretty sure that
we don't *need* to remove things from those.

The following changes since commit 23bd5300b4a99218a15f4f6b0ab4091d63a602a5:
  Richard Purdie (1):
        data_smart: Fix unanchored regexp causing strange parsing issue

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib seebs/remove
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/remove

Peter Seebach (2):
  data_smart.py: track file inclusion and variable modifications
  data_smart.py: implement _remove as a keyword like _append.

 lib/bb/cooker.py                     |    2 +
 lib/bb/data.py                       |   65 ++++++++--
 lib/bb/data_smart.py                 |  220 +++++++++++++++++++++++++++-------
 lib/bb/parse/__init__.py             |    6 +-
 lib/bb/parse/ast.py                  |   76 +++++++-----
 lib/bb/parse/parse_py/ConfHandler.py |    6 +-
 6 files changed, 286 insertions(+), 89 deletions(-)




             reply	other threads:[~2012-08-16  1:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  1:14 Peter Seebach [this message]
2012-08-16  1:14 ` [PATCH 1/2] data_smart.py: track file inclusion and variable modifications Peter Seebach
2012-08-16 14:32   ` Richard Purdie
2012-08-16 16:39     ` Peter Seebach
2012-08-17 10:09       ` Richard Purdie
2012-08-16  1:14 ` [PATCH 2/2] data_smart.py: implement _remove as a keyword like _append Peter Seebach
2012-08-16 10:13   ` Richard Purdie
2012-08-16 13:32     ` Peter Seebach

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=cover.1345079338.git.peter.seebach@windriver.com \
    --to=peter.seebach@windriver.com \
    --cc=bitbake-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox