From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: [bitbake][RFC PATCH 0/1] Proposed fix for layer branch mismatch issue
Date: Thu, 29 Jan 2015 13:49:51 +0000 [thread overview]
Message-ID: <cover.1422539142.git.paul.eggleton@linux.intel.com> (raw)
RFC - ccing the OE-Core list for review. If we apply this, do people
think we can commit to updating the LAYERVERSION in OE-Core at least on
every release and setting versioned LAYERDEPENDS in other layers so that
users get a sensible error if they use incompatible branches? (This also
provides us with a mechanism to handle these types of issues across
changes in master, as well.)
Thoughts?
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
The following changes since commit 9b5b1bd7d77e3f5886f6c557d3b750de1f6d6025:
siggen: Ensure taskdata default functions exist in base class (2015-01-23 14:39:40 +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 (1):
cooker: rework LAYERDEPENDS versioning so that it is actually useful
lib/bb/cooker.py | 36 +++++++++---------------------------
lib/bb/utils.py | 22 ++++++++++++++++++++++
2 files changed, 31 insertions(+), 27 deletions(-)
--
1.9.3
next reply other threads:[~2015-01-29 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 13:49 Paul Eggleton [this message]
2015-01-29 13:49 ` [RFC bitbake][RFC PATCH 1/1] cooker: rework LAYERDEPENDS versioning so that it is actually useful Paul Eggleton
2015-01-29 17:25 ` [bitbake-devel] " Mark Hatle
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.1422539142.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox