From: Jacob Kroon <jacob.kroon@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Luca Bocassi <luca.boccassi@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 1/2] poky-altcfg: enable usrmerge
Date: Thu, 14 Jul 2022 13:15:21 +0200 [thread overview]
Message-ID: <cd66e245-9b30-dc6f-ed7e-a2d9a67df98c@gmail.com> (raw)
In-Reply-To: <8189a37bf619f781f8e9437fd5a4b2c7c06c7457.camel@linuxfoundation.org>
On 7/13/22 19:53, Richard Purdie wrote:
> On Wed, 2022-07-13 at 17:55 +0100, Luca Bocassi wrote:
>> From: Luca Boccassi <luca.boccassi@microsoft.com>
>>
>> Ensure it gets tested by the CI
>>
>> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
>> ---
>> meta-poky/conf/distro/poky-altcfg.conf | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/meta-poky/conf/distro/poky-altcfg.conf b/meta-poky/conf/distro/poky-altcfg.conf
>> index f03306e798..57a76e8bb9 100644
>> --- a/meta-poky/conf/distro/poky-altcfg.conf
>> +++ b/meta-poky/conf/distro/poky-altcfg.conf
>> @@ -9,6 +9,8 @@ DISTROOVERRIDES = "poky:poky-altcfg"
>> #DISTROOVERRIDES = "poky:linuxstdbase"
>>
>> INIT_MANAGER:poky-altcfg = "systemd"
>> +# systemd will soon require usrmerge
>> +DISTRO_FEATURES:poky-altcfg += "usrmerge"
>> # systemd isn't suitable with musl
>> INIT_MANAGER:poky-altcfg:libc-musl = "sysvinit"
>>
>
> This blew up builds since it clears everything else out of
> DISTRO_FEATURES which isn't what was intended. I've tweaked the patch
> and re-queued.
>
Maybe I'm missing something, but what is the benefit in introducing and
using the "poky-altcfg" override in this file ? If DISTRO_FEATURES was
just appended with
DISTRO_FEATURES += "usrmerge"
it would all be fine, since it is after the
require conf/distro/poky.conf
line, right ? And if someone wants to base a distro in
"poky-altcfg.conf", they would include "poky-altcfg.conf" first in the
same way, then do customizations.
Jacob
prev parent reply other threads:[~2022-07-14 11:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 20:29 [PATCH] systemd: add usrmerge to REQUIRED_DISTRO_FEATURES luca.boccassi
2022-07-11 22:06 ` [OE-core] " Richard Purdie
2022-07-12 17:16 ` Luca Boccassi
2022-07-12 21:55 ` Richard Purdie
2022-07-12 23:30 ` Luca Boccassi
2022-07-13 13:19 ` Richard Purdie
2022-07-13 15:52 ` Luca Boccassi
2022-07-13 17:00 ` Alexander Kanavin
2022-10-19 18:10 ` Luca Boccassi
2022-07-13 15:41 ` [PATCH v2 1/2] poky-altcfg: enable usrmerge luca.boccassi
2022-07-13 15:41 ` [PATCH v2 2/2] systemd: add usrmerge to REQUIRED_DISTRO_FEATURES luca.boccassi
2022-07-13 15:57 ` [OE-core] " Martin Jansa
[not found] ` <17016EB5AC5A56BC.15323@lists.openembedded.org>
2022-07-13 16:00 ` Martin Jansa
2022-07-13 16:26 ` Richard Purdie
2022-07-13 16:55 ` Luca Boccassi
2022-07-13 20:55 ` Richard Purdie
2022-07-13 16:55 ` [PATCH v3 1/2] poky-altcfg: enable usrmerge luca.boccassi
2022-07-13 16:55 ` [PATCH v3 2/2] systemd: add usrmerge to REQUIRED_DISTRO_FEATURES luca.boccassi
2022-07-13 17:53 ` [OE-core] [PATCH v3 1/2] poky-altcfg: enable usrmerge Richard Purdie
2022-07-13 18:09 ` Luca Boccassi
2022-07-13 18:36 ` Richard Purdie
2022-07-13 19:02 ` Luca Boccassi
2022-07-13 21:17 ` Richard Purdie
2022-07-13 22:56 ` Andre McCurdy
2022-07-14 11:15 ` Jacob Kroon [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=cd66e245-9b30-dc6f-ed7e-a2d9a67df98c@gmail.com \
--to=jacob.kroon@gmail.com \
--cc=luca.boccassi@gmail.com \
--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 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.