From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>, meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago][master][PATCH] layer.conf: Update LAYERSERIES_COMPAT for mickledore
Date: Mon, 9 Jan 2023 12:06:52 -0500 [thread overview]
Message-ID: <20230109170652.GS22689@denix.org> (raw)
In-Reply-To: <1eb78db5-b5ac-5893-8f24-405e40a76c2a@ti.com>
On Thu, Jan 05, 2023 at 10:12:59AM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
>
>
> On 1/4/2023 16:44, Denys Dmytriyenko wrote:
> >On Wed, Jan 04, 2023 at 04:15:48PM -0600, Ryan Eatmon wrote:
> >>
> >>
> >>On 1/4/2023 4:00 PM, Denys Dmytriyenko wrote:
> >>>On Wed, Jan 04, 2023 at 03:17:11PM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
> >>>>oe-core switched to mickedore [1]
> >>>>
> >>>>[1] https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f
> >>>>
> >>>>Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> >>>>---
> >>>> meta-arago-distro/conf/layer.conf | 2 +-
> >>>> meta-arago-extras/conf/layer.conf | 2 +-
> >>>> 2 files changed, 2 insertions(+), 2 deletions(-)
> >>>>
> >>>>diff --git a/meta-arago-distro/conf/layer.conf b/meta-arago-distro/conf/layer.conf
> >>>>index 5de46fc9..1ffcd2fb 100644
> >>>>--- a/meta-arago-distro/conf/layer.conf
> >>>>+++ b/meta-arago-distro/conf/layer.conf
> >>>>@@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "meta-arago-distro"
> >>>> BBFILE_PATTERN_meta-arago-distro := "^${LAYERDIR}/"
> >>>> BBFILE_PRIORITY_meta-arago-distro = "10"
> >>>>-LAYERSERIES_COMPAT_meta-arago-distro = "kirkstone langdale"
> >>>>+LAYERSERIES_COMPAT_meta-arago-distro = "mickledore"
> >>>
> >>>Do you want to keep existing compatibility around for a bit longer?
> >>
> >>Is it worth keeping it around? All of our testing is being done
> >>with master for everything. How many people do you think are using
> >>an older version of bitbake with the latest master of
> >>meta-ti/meta-arago? I would think they are likely pointing to
> >>latest of everything if they are doing anything.
> >
> >You have to provide *some* branch that is compatible with langdale for people
> >who has their products based on langdale release and wanting to use meta-ti
> >and/or meta-arago. It could be master, or it could be a separately langdale
> >branch, if you are willing to do that instead.
> >
> >I see you already merged Khem's v1 patch to meta-ti, which means there's
> >currently NO branches compatible with langdale! Even though TI does not
> >officially test and support langdale, you should not actively prevent people
> >from using it in their products with meta-ti, per the earlier message:
> >https://lists.yoctoproject.org/g/meta-ti/message/15137
>
>
> Ok. I see what you are saying and we should support both of them.
> I'll get that fixed.
Ping. meta-ti has been failing on YP Autobuilder for almost a week now!
> >>>> LAYERDEPENDS_meta-arago-distro = " \
> >>>> core \
> >>>>diff --git a/meta-arago-extras/conf/layer.conf b/meta-arago-extras/conf/layer.conf
> >>>>index e2c8119f..9cdfcb32 100644
> >>>>--- a/meta-arago-extras/conf/layer.conf
> >>>>+++ b/meta-arago-extras/conf/layer.conf
> >>>>@@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "meta-arago-extras"
> >>>> BBFILE_PATTERN_meta-arago-extras := "^${LAYERDIR}/"
> >>>> BBFILE_PRIORITY_meta-arago-extras = "10"
> >>>>-LAYERSERIES_COMPAT_meta-arago-extras = "kirkstone langdale"
> >>>>+LAYERSERIES_COMPAT_meta-arago-extras = "mickledore"
> >>>> # Set a variable to get to the top of the metadata location
> >>>> ARAGOBASE := '${@os.path.normpath("${LAYERDIR}/../")}'
> >>>>--
> >>>>2.17.1
prev parent reply other threads:[~2023-01-09 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 21:17 [meta-arago][master][PATCH] layer.conf: Update LAYERSERIES_COMPAT for mickledore Ryan Eatmon
2023-01-04 22:00 ` Denys Dmytriyenko
2023-01-04 22:15 ` Ryan Eatmon
2023-01-04 22:44 ` Denys Dmytriyenko
2023-01-05 16:12 ` Ryan Eatmon
2023-01-09 17:06 ` Denys Dmytriyenko [this message]
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=20230109170652.GS22689@denix.org \
--to=denis@denix.org \
--cc=meta-arago@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.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.