From: "Adrian Bunk" <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Christian Eggers <ceggers@arri.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Patches are stuck in master-next
Date: Wed, 8 Jul 2020 18:51:23 +0300 [thread overview]
Message-ID: <20200708155123.GE5419@localhost> (raw)
In-Reply-To: <4b2516f1c16b7eff3fbedf15083bfc7c06aaad36.camel@linuxfoundation.org>
On Wed, Jul 08, 2020 at 04:35:21PM +0100, Richard Purdie wrote:
> On Wed, 2020-07-08 at 17:07 +0200, Christian Eggers wrote:
> > From Richard I got no response to the question whether
> > potentially every package may be extended for nativesdk/native,
> > or these platforms a reserved for packages required for "building".
>
> There needs to be a sensible use case for extending them. It doesn't
> come for free and increases parse time for each extension added.
My biggest worry is a different one:
Native is built by the host compiler, and Yocto stable series aim at
supporting hosts with future distributions. Something like "building
dunfell on hosts with gcc 11" is easier when there are fewer recipes
that have to be patched.
> Cheers,
>
> Richard
cu
Adrian
prev parent reply other threads:[~2020-07-08 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 6:20 Patches are stuck in master-next Christian Eggers
2020-07-08 9:20 ` [OE-core] " Richard Purdie
2020-07-08 9:40 ` Christian Eggers
2020-07-08 9:53 ` Richard Purdie
2020-07-08 14:20 ` Adrian Bunk
2020-07-08 15:07 ` Christian Eggers
2020-07-08 15:35 ` Richard Purdie
2020-07-08 15:51 ` Adrian Bunk [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=20200708155123.GE5419@localhost \
--to=bunk@stusta.de \
--cc=ceggers@arri.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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