From: Tan Siewert <tan.siewert@9elements.com>
To: Paul Barker <paul@pbarker.dev>, openembedded-core@lists.openembedded.org
Cc: Sai Sireesha T <saisireesha.t@windriver.com>,
Patrick Williams <patrick@stwcx.xyz>
Subject: Re: [PATCH 1/4] systemd: add ukify packageconfig
Date: Wed, 28 Oct 2026 15:48:14 +0100 [thread overview]
Message-ID: <17d13fd2-4b74-4a80-b4be-c4172ab73ed9@9elements.com> (raw)
In-Reply-To: <d35ce037b83bad3100142b3715e793b2f41d6474.camel@pbarker.dev>
On 10/23/26 1:34 PM, Paul Barker wrote:
> On Fri, 2026-10-23 at 12:51 +0200, Tan Siewert wrote:
>> systemd gates ukify via allowed(), so it is built and installed unless
>> explicitly disabled.
>>
>> Add a packageconfig option that is enabled by default when the efi
>> DISTRO_FEATURE is set. It can still be removed if wanted, which may be
>> useful when using meta-tpm, which may include ukify implicitly.
>>
>> Signed-off-by: Tan Siewert <tan.siewert@9elements.com>
>
> [snip]
>
>> @@ -405,7 +407,7 @@ PACKAGE_BEFORE_PN += "\
>> ${PN}-networkd \
>> ${PN}-rpm-macros \
>> ${PN}-udev-rules \
>> - ${PN}-ukify \
>> + ${@bb.utils.contains('PACKAGECONFIG', 'ukify', '${PN}-ukify', '', d)} \
>
> Does the package really need to be removed here? If it is empty then
> do_package should not create it. If there are still files that would
> otherwise end up in ${PN}-ukify then removing the package entry may
> cause them to be silently included in a later package.
>
Sorry for the late response.
Probably not. I may have overlooked it when checking the logs if
do_package built an empty package or not (and I didn't think about the
side-effects of it that you describe).
I'll remove the condition in v2.
Thanks!
Tan
next prev parent reply other threads:[~2026-10-28 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 10:51 [PATCH 0/4] systemd: add packageconfigs for storage optimisation Tan Siewert
2026-10-23 10:51 ` [PATCH 1/4] systemd: add ukify packageconfig Tan Siewert
2026-10-23 11:34 ` Paul Barker
2026-10-28 14:48 ` Tan Siewert [this message]
2026-10-23 10:51 ` [PATCH 2/4] systemd: add sysinstall packageconfig Tan Siewert
2026-10-23 10:51 ` [PATCH 3/4] systemd: add hwdb packageconfig Tan Siewert
2026-10-23 10:51 ` [PATCH 4/4] systemd: add fdisk packageconfig Tan Siewert
2026-10-23 20:00 ` [PATCH 0/4] systemd: add packageconfigs for storage optimisation Tirumala Pudi, Sai Sireesha
2026-10-28 14:50 ` Tan Siewert
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=17d13fd2-4b74-4a80-b4be-c4172ab73ed9@9elements.com \
--to=tan.siewert@9elements.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick@stwcx.xyz \
--cc=paul@pbarker.dev \
--cc=saisireesha.t@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox