From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: uvv.mail@gmail.com
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] systemd: Build the systemctl executable
Date: Mon, 3 Feb 2025 09:54:04 +0200 [thread overview]
Message-ID: <Z6B2HKSlI6k9wNXO@nuoska> (raw)
In-Reply-To: <20250202200319.82231-3-uvv.mail@gmail.com>
Hi,
On Sun, Feb 02, 2025 at 09:03:19PM +0100, Vyacheslav Yurkov via lists.openembedded.org wrote:
> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
>
> Instead of the python re-implementation build the actual systemctl from
> the systemd source tree.
Could you elaborate why? Some usecase or feature not supported by the python
wrapper? Which one?
Maybe it makes sense to have a self or runtime test for this usecase.
Then the native toolchain set seems to be increasing. While systemd-boot-native
is also trying to be simple for ukify.py, it could expand if tools like
systemd-measure for TPM calculations would get added. And systemd-sbsign instead of
sbsign for secureboot signatures.
Maybe it would make sense to cambine all in a full systemd-native recipe?
> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
> ---
> .../systemd/systemd-systemctl-native.bb | 20 +-
> ...-meson-add-install-tag-for-systemctl.patch | 24 ++
> .../systemd/systemd-systemctl/systemctl | 366 ------------------
> 3 files changed, 32 insertions(+), 378 deletions(-)
> create mode 100644 meta/recipes-core/systemd/systemd-systemctl/0001-meson-add-install-tag-for-systemctl.patch
> delete mode 100755 meta/recipes-core/systemd/systemd-systemctl/systemctl
>
> diff --git a/meta/recipes-core/systemd/systemd-systemctl-native.bb b/meta/recipes-core/systemd/systemd-systemctl-native.bb
> index ffa024caef..57bb1ab830 100644
> --- a/meta/recipes-core/systemd/systemd-systemctl-native.bb
> +++ b/meta/recipes-core/systemd/systemd-systemctl-native.bb
> @@ -1,17 +1,13 @@
> -SUMMARY = "Wrapper for enabling systemd services"
> +SUMMARY = "Systemctl executable from systemd"
>
> -LICENSE = "MIT"
> -LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> +require systemd.inc
>
> +DEPENDS = "gperf-native libcap-native util-linux-native python3-jinja2-native"
>
> -inherit native
> +inherit pkgconfig meson native
>
> -SRC_URI = "file://systemctl"
> +SRC_URI = "file://0001-meson-add-install-tag-for-systemctl.patch"
>
> -S = "${WORKDIR}/sources"
> -UNPACKDIR = "${S}"
> -
> -do_install() {
> - install -d ${D}${bindir}
> - install -m 0755 ${S}/systemctl ${D}${bindir}
> -}
> +MESON_TARGET = "systemctl:executable"
> +MESON_INSTALL_TAGS = "systemctl"
> +EXTRA_OEMESON:append = " -Dlink-systemctl-shared=false"
> diff --git a/meta/recipes-core/systemd/systemd-systemctl/0001-meson-add-install-tag-for-systemctl.patch b/meta/recipes-core/systemd/systemd-systemctl/0001-meson-add-install-tag-for-systemctl.patch
> new file mode 100644
> index 0000000000..a4b3e5a47e
> --- /dev/null
> +++ b/meta/recipes-core/systemd/systemd-systemctl/0001-meson-add-install-tag-for-systemctl.patch
> @@ -0,0 +1,24 @@
> +From fe2eb1dde51648b0e5825766e2f27a859de8521c Mon Sep 17 00:00:00 2001
> +From: Vyacheslav Yurkov <uvv.mail@gmail.com>
> +Date: Sun, 2 Feb 2025 10:13:38 +0100
> +Subject: [PATCH] meson: add install tag for systemctl
> +
> +Upstream-Status: Submitted
Would be nice to link the URL here.
Cheers,
-Mikko
next prev parent reply other threads:[~2025-02-03 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 20:03 [PATCH 1/3] bitbake.conf: Add conditional host tool getent uvv.mail
2025-02-02 20:03 ` [PATCH 2/3] meson.bbclass: Add an option to specify install tags uvv.mail
2025-02-02 20:03 ` [PATCH 3/3] systemd: Build the systemctl executable uvv.mail
2025-02-02 20:17 ` Patchtest results for " patchtest
2025-02-03 7:54 ` Mikko Rapeli [this message]
2025-02-03 11:07 ` [OE-core] " Alexander Kanavin
2025-02-03 11:27 ` Mikko Rapeli
2025-02-03 11:32 ` Alexander Kanavin
2025-02-03 11:37 ` Mikko Rapeli
2025-02-03 8:53 ` Ross Burton
2025-02-03 9:35 ` Alex Kiernan
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=Z6B2HKSlI6k9wNXO@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=uvv.mail@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.