From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: wfan@windriver.com
Subject: Re: [PATCH] meta-networking: Add LAYERVERSION and LAYERDEPENDS
Date: Mon, 18 Mar 2013 11:18:44 -0400 [thread overview]
Message-ID: <20130318151844.GA9185@windriver.com> (raw)
In-Reply-To: <1599644.gZKTPRS2fY@helios>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
Getting caught up ...
[Re: [oe] [PATCH] meta-networking: Add LAYERVERSION and LAYERDEPENDS] On 13.03.11 (Mon 15:38) Paul Eggleton wrote:
> On Monday 11 March 2013 17:38:39 wenzong.fan@windriver.com wrote:
> > From: Wenzong Fan <wenzong.fan@windriver.com>
> >
> > Add LAYERVERSION and LAYERDEPENDS to layer.conf
> >
> > Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
> > ---
> > meta-networking/conf/layer.conf | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/meta-networking/conf/layer.conf
> > b/meta-networking/conf/layer.conf index 1ea2bc2..f75080a 100644
> > --- a/meta-networking/conf/layer.conf
> > +++ b/meta-networking/conf/layer.conf
> > @@ -9,3 +9,8 @@ BBFILE_COLLECTIONS += "networking"
> > BBFILE_PATTERN_networking := "^${LAYERDIR}/"
> > BBFILE_PRIORITY_networking = "5"
> >
> > +# This should only be incremented on significant changes that will
> > +# cause compatibility issues with other layers
> > +LAYERVERSION_networking = "1"
> > +
> > +LAYERDEPENDS_networking = "core"
>
> This is good, but it might be useful to also set a versioned dependency on the
> core - that way if you attempt to use the denzil branch of OE-Core with master
> of one of these layers, instead of an error about incorrect indentation in
> python functions you get one specifically about the version being incorrect.
I agree. This seems to have caused at least one person some headache
recently and I know I've had a few head-scratching moments when I was
burned by different trees being on incompatible branches.
Was there an update on this that I didn't see yet? Or are you planning
one, Wenzong? I can merge this now, but Paul's got a very good point, I
think.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-03-18 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 9:38 [PATCH] meta-networking: Add LAYERVERSION and LAYERDEPENDS wenzong.fan
2013-03-11 15:38 ` Paul Eggleton
2013-03-18 15:18 ` Joe MacDonald [this message]
2013-03-18 19:22 ` Joe MacDonald
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=20130318151844.GA9185@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=wfan@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox