All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Larson <kergoth@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH 0/2] Only try to expand refs to valid variable names
Date: Fri, 18 Jan 2019 21:45:53 +0500	[thread overview]
Message-ID: <cover.1547829050.git.chris_larson@mentor.com> (raw)

From: Christopher Larson <chris_larson@mentor.com>

This aligns the behavior of expansion with the recipe parser, only
attempting to expand references to valid variable names. This avoids
adding references for things like `${foo#${TOPDIR}}` to our vardeps
without imposing much additional processing overhead beyond the change
to the expansion regexp.

YOCTO #12987

The following changes since commit 610dbee5634677f5055e2b36a3043cd197fb8c51:

  gitsm.py: Refactor the functions and simplify the class (2019-01-15 22:22:29 +0000)

are available in the Git repository at:

  git@github.com:kergoth/bitbake yocto-12987-new

for you to fetch changes up to 9cb64e9781c98f1aaa42571af54655eaf6816583:

  bb.tests.codeparser: add parameter expansion modifiers test (2019-01-16 19:46:10 +0000)

----------------------------------------------------------------
Christopher Larson (2):
      bb.data_smart: only try to expand refs to valid variable names
      bb.tests.codeparser: add parameter expansion modifiers test

 lib/bb/data_smart.py       | 2 +-
 lib/bb/tests/codeparser.py | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)

-- 
2.17.1



             reply	other threads:[~2019-01-18 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 16:45 Christopher Larson [this message]
2019-01-18 16:45 ` [PATCH 1/2] bb.data_smart: only try to expand refs to valid variable names Christopher Larson
2019-01-18 16:45 ` [PATCH 2/2] bb.tests.codeparser: add parameter expansion modifiers test Christopher Larson
2019-01-18 16:47 ` [PATCH 0/2] Only try to expand refs to valid variable names Christopher Larson

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.1547829050.git.chris_larson@mentor.com \
    --to=kergoth@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=chris_larson@mentor.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.