From: Denys Dmytriyenko <denis@denix.org>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: Ryan Eatmon <reatmon@ti.com>,
meta-arago@lists.yoctoproject.org, g-gupta@ti.com
Subject: Re: [oe-layersetup PATCH] configs: Update Kirkstone config for sysrepo
Date: Tue, 20 Jun 2023 12:13:24 -0400 [thread overview]
Message-ID: <20230620161324.GI1518@denix.org> (raw)
In-Reply-To: <089e1c0a-2d7b-21a6-91f5-3d745bf4e388@ti.com>
On Tue, Jun 20, 2023 at 09:36:12AM +0530, Ravi Gunasekaran wrote:
>
>
> On 6/20/2023 3:34 AM, Ryan Eatmon wrote:
> >
> >
> > On 6/18/2023 11:34 PM, Ravi Gunasekaran wrote:
> >> Denys,
> >>
> >> On 6/17/23 1:18 AM, Denys Dmytriyenko wrote:
> >>> On Fri, Jun 16, 2023 at 02:15:38PM +0530, Ravi Gunasekaran wrote:
> >>>> NETCONF/YANG is implemented through netopeer2/sysrepo.
> >>>> A Yocto project for sysrepo is available in public domain[1].
> >>>>
> >>>> [1] is compatible only with Yocto Honister branch. So update
> >>>> the config with [2] which is fork of [1] for Kirkstone.
> >>>>
> >>>> [1] - https://github.com/sartura/meta-sysrepo
> >>>> [2] - https://github.com/ravig07/meta-sysrepo
> >>>
> >>> So, you are bumping many of the recipes in that layer, plus updating to the
> >>> new override syntax and setting compatibility with kirkstone. The PR has been
> >>> setting open since May 4 w/o any comments, so it's probably safe to assume the
> >>> layer is abandoned. Why not move the recipes to an active layer? At least to
> >>> meta-arago, or even better work on upstreaming them to meta-openembedded?
> >>>
> >>> Regardless, the changes for kirkstone appear to be safe to langdale and
> >>> mickledore - that would allow including the change in master builds too.
> >>
> >> Yes, the PR has been open since quite some time.
> >> I did think of adding the recipes to meta-arago, but since the recipes already
> >> exists in the public domain, I felt moving them to meta-arago might not be the
> >> right way.
> >
> > We should pull any needed recipes into meta-arago and not in a forked repo of
> > meta-sysrepo...
> >
> > Are you signing up to maintain your forked copy of meta-sysrepo for all time?
> > If not, then we should migrate your required changes into meta-arago-extras
> > and just deal with the fact that we as TI need to maintain them.
> >
>
> Understood. I will add the recipes to meta-aragos-extras then.
What is "aragos"?
> >>>> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
> >>>> ---
> >>>> I have sent a Pull Request for [2]. Once it gets merged, then the URI
> >>>> in the config.txt can be replaced with it.
> >>>>
> >>>> configs/arago-kirkstone-config.txt | 1 +
> >>>> 1 file changed, 1 insertion(+)
> >>>>
> >>>> diff --git a/configs/arago-kirkstone-config.txt
> >>>> b/configs/arago-kirkstone-config.txt
> >>>> index c2524a4..e80ab80 100644
> >>>> --- a/configs/arago-kirkstone-config.txt
> >>>> +++ b/configs/arago-kirkstone-config.txt
> >>>> @@ -10,6 +10,7 @@
> >>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,
> >>>>
> >>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp
> >>>>
> >>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
> >>>>
> >>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
> >>>> +meta-sysrepo,https://github.com/ravig07/meta-sysrepo,kirkstone,HEAD,layers=
> >>>> OECORELAYERCONF=./sample-files/bblayers.conf.sample
> >>>> OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> >>>> BITBAKE_INCLUSIVE_VARS=yes
> >>>> --
> >>>> 2.17.1
next prev parent reply other threads:[~2023-06-20 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 8:45 [oe-layersetup PATCH] configs: Update Kirkstone config for sysrepo Ravi Gunasekaran
2023-06-16 19:48 ` Denys Dmytriyenko
2023-06-19 4:34 ` Ravi Gunasekaran
2023-06-19 22:04 ` Ryan Eatmon
2023-06-20 4:06 ` Ravi Gunasekaran
2023-06-20 16:13 ` Denys Dmytriyenko [this message]
2023-06-21 4:28 ` Ravi Gunasekaran
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=20230620161324.GI1518@denix.org \
--to=denis@denix.org \
--cc=g-gupta@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=r-gunasekaran@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.