From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Cc: Alexander Kanavin <alexander.kanavin@intel.com>
Subject: LAYERSERIES
Date: Fri, 06 Apr 2018 11:37:01 +0100 [thread overview]
Message-ID: <1523011021.2942.6.camel@linuxfoundation.org> (raw)
I finally found 5 mins to sit and look at where I'd gotten to with the
LAYERSERIES variable handling. I sent out discussion about this a while
ago but as a reminder:
We have a problem where people expect master branch of meta-X to work
with OE-Core master. If meta-X hasn't been maintained for a long time,
this may give all kinds of weird errors. This creates a large support
burden and means we struggle to spot unmaintained/un-updated layers.
We'd like to fix this.
In answer to this I added LAYERSERIES_CORENAMES to OE-Core and strongly
suggest layers then set:
LAYERSERIES_COMPAT_xxx = "sumo"
in their layer.conf where xxx is the collection name (used elsewhere in
layer.conf) to indicate which versions of OE-Core they're expected to
work against.
The code already exists to validate this with a fatal error for
mismatches. What was missing was:
a) to print a warning if LAYERSERIES_COMPAT_xxx is unset. I've a patch
queued for bitbake to add this.
b) add a check to yocto-check-layer and require this to be set for YP
Compatible v2. I've added
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12661
to track this.
Yes, its late in the release and the warnings will be annoying but I
think its worth fixing this now so I'm pushing ahead to resolve this.
Cheers,
Richard
next reply other threads:[~2018-04-06 10:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 10:37 Richard Purdie [this message]
2018-04-06 14:16 ` [Openembedded-architecture] LAYERSERIES Trevor Woerner
2018-04-06 15:29 ` Richard Purdie
2018-04-06 18:16 ` Scott Rifenbark
2018-04-06 22:25 ` Richard Purdie
2018-04-06 22:44 ` Scott Rifenbark
2018-04-07 14:13 ` Richard Purdie
2018-04-06 18:25 ` Martin Jansa
2018-04-06 22:00 ` Richard Purdie
2018-04-06 20:46 ` akuster808
2018-04-06 21:56 ` Richard Purdie
2018-04-14 21:48 ` Trevor Woerner
2018-04-15 21:12 ` Richard Purdie
2018-04-06 18:58 ` Denys Dmytriyenko
2018-04-06 21:52 ` Richard Purdie
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=1523011021.2942.6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@intel.com \
--cc=openembedded-architecture@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