From: Markus Volk <f_l_k@t-online.de>
To: alex.kanavin@gmail.com
Cc: "Alexander Kanavin via lists.openembedded.org"
<alex.kanavin=gmail.com@lists.openembedded.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC][oe-core][PATCH] systemd: dont allow autoselect for meson
Date: Sun, 10 Nov 2024 15:52:26 +0100 [thread overview]
Message-ID: <EBPQMS.UEZLLM5MH6D9@t-online.de> (raw)
In-Reply-To: <CANNYZj8XUkrp6Fc5kB=4S_q7AKiYkN+zZ4Tqd9ZEQK-4JGC5xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Sun, Nov 10 2024 at 03:40:42 PM +01:00:00, Alexander Kanavin via
lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
wrote:
> It would help to explain what the option does precisely.
As far as I understand it, it is a general way for meson to prevent the
addition of features just because the required source has been found.
Each feature must then be explicitly enabled.
I checked if the setting is effective by creating sysupdate. If
auto-features=enabled, it was enough to add util-linux to the
PACKAGECONFIG[sysuser] depends field and fdisk support was built
without having to explicitly set -Dfdisk=enabled. With
'--auto-features=disabled' the latter was required.
[-- Attachment #2: Type: text/html, Size: 883 bytes --]
next prev parent reply other threads:[~2024-11-10 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 13:28 [RFC][oe-core][PATCH] systemd: dont allow autoselect for meson Markus Volk
2024-11-10 14:40 ` Alexander Kanavin
2024-11-10 14:52 ` Markus Volk [this message]
[not found] ` <1806A2E5B9CEF1AC.19665@lists.openembedded.org>
2024-11-10 15:23 ` Markus Volk
2024-11-10 16:33 ` Alexander Kanavin
2024-11-10 16:43 ` Markus Volk
2024-11-11 11:03 ` Alexander Kanavin
2024-11-11 13:31 ` Ross Burton
2024-11-12 6:51 ` Markus Volk
2024-11-11 7:07 ` ChenQi
2024-11-11 9:48 ` Markus Volk
2024-11-11 10:49 ` Alexander Kanavin
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=EBPQMS.UEZLLM5MH6D9@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin=gmail.com@lists.openembedded.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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