From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] systemd: Allow native build
Date: Thu, 30 Mar 2023 16:08:49 +0200 [thread overview]
Message-ID: <869f611a-1645-52b6-1f3b-e4b605f2ddd4@gmail.com> (raw)
In-Reply-To: <a25c3a41d623242edf004723dc94518228cfc1da.camel@linuxfoundation.org>
2023. 03. 30. 15:50 keltezéssel, Richard Purdie írta:
> On Thu, 2023-03-30 at 15:42 +0200, Zoltan Boszormenyi wrote:
>> systemd-native is a dependency for libgudev-native, which
>> in turn is a dependency for libfprint-native, which is needed
>> to build libfprint.
>>
>> The native systemctl binary is removed so it doesn't conflict
>> with the script from systemd-systemctl-native.
>>
>> TODO? The new natively built systemctl binary may replace
>> the script in systemd-systemctl-native, as it supports
>> more options and works better than the script. For example,
>> the current script does not create the symlinks in
>> /etc/systemd/system for WantedBy= and RequiredBy= settings
>> and does not support systemctl set-default some.target.
> Which piece of systemd is libfprint needing?
Please see the MR:
https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/431
udev (provided by systemd) -> libgudev -> libfprint
also:
udev-native -> libgudev-native -> libfprint-native -> libfprint
Also, please read the TODO part of the patch for systemd
and consider it.
Thanks.
>
> We've had a request for systemd-native before and my opinion on it
> hasn't changed, I'd much prefer not to have it.
>
> Cheers,
>
> Richard
next prev parent reply other threads:[~2023-03-30 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 13:42 [PATCH 1/2] systemd: Allow native build Zoltán Böszörményi
2023-03-30 13:42 ` [PATCH 2/2] libgudev: " Zoltán Böszörményi
2023-03-30 13:47 ` [OE-core] " Alexander Kanavin
2023-03-30 14:01 ` Böszörményi Zoltán
2023-03-30 13:46 ` [OE-core] [PATCH 1/2] systemd: " Alexander Kanavin
2023-03-30 14:04 ` Böszörményi Zoltán
2023-03-30 13:50 ` Richard Purdie
2023-03-30 14:08 ` Böszörményi Zoltán [this message]
2023-03-30 14:10 ` Alexander Kanavin
2023-03-30 14:31 ` Böszörményi Zoltán
2023-03-30 14:41 ` Alexander Kanavin
2023-03-30 14:51 ` Böszörményi Zoltán
2023-03-30 14:57 ` Alexander Kanavin
[not found] ` <175138E3E9EE1FF1.27612@lists.openembedded.org>
2023-03-30 14:45 ` Böszörményi Zoltán
2023-03-30 16:39 ` Richard Purdie
2023-03-31 9:39 ` Böszörményi Zoltán
[not found] ` <1751778F66ADC2DD.27612@lists.openembedded.org>
2023-03-31 9:46 ` Böszörményi Zoltán
2023-04-03 10:59 ` Ross Burton
2023-04-03 13:00 ` Böszörményi Zoltán
2023-04-03 19:52 ` Ross Burton
2023-04-04 8:31 ` Böszörményi Zoltán
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=869f611a-1645-52b6-1f3b-e4b605f2ddd4@gmail.com \
--to=zboszor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox