From: "Jon Mason" <jdmason@kudzu.us>
To: Joshua Watt <JPEWhacker@gmail.com>
Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>,
meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm][PATCH] meta-arm: Remove meta-python dependency
Date: Mon, 1 Jun 2020 17:31:41 -0400 [thread overview]
Message-ID: <20200601213141.GA31505@kudzu.us> (raw)
In-Reply-To: <CAJdd5Gag=0HF8+5KiF0DoLG1WZs+0ngbnT7G8CS1dFa=ydqjoQ@mail.gmail.com>
On Sat, May 30, 2020 at 01:39:49PM -0500, Joshua Watt wrote:
> On Fri, May 29, 2020, 10:37 AM Bertrand Marquis <Bertrand.Marquis@arm.com>
> wrote:
>
> >
> >
> > > On 29 May 2020, at 16:32, Joshua Watt <JPEWhacker@gmail.com> wrote:
> > >
> > >
> > > On 5/29/20 10:21 AM, Bertrand Marquis wrote:
> > >>
> > >>> On 29 May 2020, at 16:14, Joshua Watt via lists.yoctoproject.org
> > <JPEWhacker=gmail.com@lists.yoctoproject.org> wrote:
> > >>>
> > >>> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> > >>> ---
> > >>> meta-arm/conf/layer.conf | 3 +--
> > >>> 1 file changed, 1 insertion(+), 2 deletions(-)
> > >>>
> > >>> diff --git a/meta-arm/conf/layer.conf b/meta-arm/conf/layer.conf
> > >>> index d96e9f1..1c241d4 100644
> > >>> --- a/meta-arm/conf/layer.conf
> > >>> +++ b/meta-arm/conf/layer.conf
> > >>> @@ -11,6 +11,5 @@ BBFILE_PRIORITY_meta-arm = "6"
> > >>>
> > >>> LAYERDEPENDS_meta-arm = " \
> > >>> core \
> > >>> - meta-python \
> > >>> "
> > >>> -LAYERSERIES_COMPAT_meta-arm = "warrior zeus dunfell"
> > >>> +LAYERSERIES_COMPAT_meta-arm = "gatesgarth"
> > >> Could you explain why you want to remove dunfell compatibility ?
> > >
> > > dunfell doesn't have the required python recipes in oe-core, so it isn't
> > compatible with it anymore.
> >
> > Nothing has been tested or is compatible with gatesgarth right now so this
> > change will really have a breaking impact.
> >
>
> Right, you certainly wouldn't want to backport it to the dunfell branch;
> this is just for master where the next release would be gatesgarth anyway.
>
> Also, with the qemu support I added, I think we have reasonable testing
> coverage on meta-arm, and in particular enough to have high confidence in
> this change.
>
> Finally, FWIW, upstream oe-core and meta-python have already made these
> changes on their master branches, so it seems like we wouldn't want a
> useless dependency on meta-python in meta-arm, *especially* if the idea is
> to get other bsp layers to depend on meta-arm to consolidate things like
> TF-A and optee.
We currently have a requirement for dunfell compatability on the
meta-arm master branch for Arm's BSP software releases (which will
be YP based going forward). To make a stable release for our
customers, we need to draw a line between stablity of our dependent
layers and the latest code in the meta-arm layer. This especially
relates to the BSPs Arm will be adding to meta-arm-bsp in this
release.
We do not have to keep dunfell support in master after the release of
gatesgarth, but we will need it until then. So, please stash this
patch until October (which will be here sooner than you think).
Thanks,
Jon
>
>
> > Bertrand
> >
> > >
> > >
> > >>
> > >> Bertrand
> > >>
> > >>> --
> > >>> 2.17.1
> > >>>
> > >>>
> >
> >
>
next prev parent reply other threads:[~2020-06-01 21:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 15:14 [meta-arm][PATCH] meta-arm: Remove meta-python dependency Joshua Watt
2020-05-29 15:21 ` Bertrand Marquis
2020-05-29 15:32 ` Joshua Watt
2020-05-29 15:37 ` Bertrand Marquis
2020-05-30 18:39 ` Joshua Watt
2020-06-01 21:31 ` Jon Mason [this message]
2020-06-01 21:55 ` Joshua Watt
2020-06-01 22:56 ` Jon Mason
2020-06-02 6:10 ` Nicolas Dechesne
2020-06-05 23:44 ` Denys Dmytriyenko
2020-06-08 16:03 ` Jon Mason
2020-06-02 12:51 ` Richard Purdie
2020-06-02 13:24 ` Ross Burton
2020-06-02 13:20 ` Joshua Watt
-- strict thread matches above, loose matches on Subject: below --
2020-05-29 15:18 Joshua Watt
2020-05-29 15:22 ` Bertrand Marquis
2020-05-29 15:31 ` Joshua Watt
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=20200601213141.GA31505@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Bertrand.Marquis@arm.com \
--cc=JPEWhacker@gmail.com \
--cc=meta-arm@lists.yoctoproject.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 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.