From: Denys Dmytriyenko <denis@denix.org>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "peron.clem@gmail.com" <peron.clem@gmail.com>,
"meta-arm@lists.yoctoproject.org"
<meta-arm@lists.yoctoproject.org>
Subject: Re: [meta-arm] [PATCH v2 1/2] support: add libmxml 3.3.1 recipe
Date: Fri, 21 Apr 2023 11:11:38 -0400 [thread overview]
Message-ID: <20230421151138.GA9226@denix.org> (raw)
In-Reply-To: <C6BB3F5B-314F-4D2B-BD98-3C68C2F59AD3@arm.com>
On Fri, Apr 21, 2023 at 02:06:20PM +0000, Ross Burton wrote:
> On 21 Apr 2023, at 10:07, Clément Péron via lists.yoctoproject.org <peron.clem=gmail.com@lists.yoctoproject.org> wrote:
> >
> > libmxml is required by new version of gator-daemon as it
> > has been removed from the package and is now an explicit
> > dependency.
> >
> > This is a duplicate of the recipe present in meta-oe layer.
>
> I get Denys’s objection to *requiring* meta-oe in meta-arm, but I don’t want
> to start copying recipes from meta-oe every time we need something from
> there.
>
> I feel a better solution here would be to use dynamic-layers in meta-arm.
> Denys, would you be okay with that?
Placing gator-daemon into dynamic-layers? Sure, meta-ti BSP is currently not
using it, so the dependency won't be affected. Not sure about other BSPs
depending on meta-arm though, but overall it's probably the most flexible
soltion.
--
Denys
prev parent reply other threads:[~2023-04-21 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:07 [PATCH v2 1/2] support: add libmxml 3.3.1 recipe Clément Péron
2023-04-21 9:07 ` [PATCH v2 2/2] gator-daemon: bump to 8.4.0 Clément Péron
2023-04-21 14:06 ` [meta-arm] [PATCH v2 1/2] support: add libmxml 3.3.1 recipe Ross Burton
2023-04-21 15:11 ` 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=20230421151138.GA9226@denix.org \
--to=denis@denix.org \
--cc=Ross.Burton@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=peron.clem@gmail.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.