Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] Add mechanism to catch layer branch mismatches
Date: Tue, 10 Feb 2015 18:13:22 +0000	[thread overview]
Message-ID: <cover.1423591698.git.paul.eggleton@linux.intel.com> (raw)

Changes since the earlier RFC patch:
* Removed unused regex line
* Improved validation / error handling
* Added some regression tests

Note: patch 3/3 depends on patch 1/3, so they need to go in together.


The following changes since commit 207013b6dde82f9654f9be996695c8335b95a288:

  data_smart: split expanded removal values when handling _remove (2015-02-02 16:20:42 +0000)

are available in the git repository at:

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

Paul Eggleton (3):
  utils: ensure explode_dep_versions2 raises an exception on
    invalid/missing operator
  tests: add tests for OE pre-release version formatting
  cooker: rework LAYERDEPENDS versioning so that it is actually useful

 lib/bb/cooker.py      | 40 ++++++++++++++--------------------------
 lib/bb/tests/utils.py | 37 +++++++++++++++++++++++++++++++++++++
 lib/bb/utils.py       | 26 ++++++++++++++++++++++++++
 3 files changed, 77 insertions(+), 26 deletions(-)

-- 
1.9.3



             reply	other threads:[~2015-02-10 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 18:13 Paul Eggleton [this message]
2015-02-10 18:13 ` [PATCH 1/3] utils: ensure explode_dep_versions2 raises an exception on invalid/missing operator Paul Eggleton
2015-02-10 18:13 ` [PATCH 2/3] tests: add tests for OE pre-release version formatting Paul Eggleton
2015-02-10 18:13 ` [PATCH 3/3] cooker: rework LAYERDEPENDS versioning so that it is actually useful 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=cover.1423591698.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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