From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Norbert Lange <nolange79@gmail.com>
Cc: buildroot@buildroot.org, Sen Hastings <sen@hastings.org>,
James Hilliard <james.hilliard1@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH] package/systemd: remove several Kernel config options
Date: Thu, 1 Jan 2026 23:09:04 +0100 [thread overview]
Message-ID: <20260101230904.6d78e9f5@windsurf> (raw)
In-Reply-To: <20251119154819.3416176-1-nolange79@gmail.com>
Hello Norbert, James, Marcus,
On Wed, 19 Nov 2025 16:48:18 +0100
Norbert Lange <nolange79@gmail.com> wrote:
> All those features are optional and prevent customization of the kernel.
> Forcing IPv6 is particularly nasty.
>
> This reverts parts of "package/systemd: bump to version 256.4"
>
> Signed-off-by: Norbert Lange <nolange79@gmail.com>
Thanks for the patch, and thanks everyone for participating to the
discussion.
Buildroot's "philosophy" has always been to be reasonably minimal. So I
would tend to agree with both Norbert and Marcus that we should not
enable all possible options that may be needed for all possible
use-cases. We want to enable what's needed to get our systemd package
to "work" as-is, but not necessarily every possible feature that the
user may use through systemd unit files or specific features.
However, it would be good to draw a clear line, and rather than
applying Norbert's patch as-is, I'd prefer to see a commit that cleans
up those options, with a comment on top of SYSTEMD_LINUX_CONFIG_FIXUPS
that documents our "policy" on this, like "Following what's documented
at https://github.com/systemd/systemd/blob/v257.10/README, by enabling
all mandatory options, leaving disabled only 'recommended' options,
with the exception of A, B, C because blabla".
Norbert, or Marcus, do you think you could propose something like this?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-01 22:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 15:48 [Buildroot] [PATCH] package/systemd: remove several Kernel config options Norbert Lange
2025-11-19 16:16 ` James Hilliard
2025-11-19 16:32 ` Norbert Lange
2025-11-19 16:54 ` James Hilliard
2025-11-19 17:39 ` Norbert Lange
2025-11-19 17:44 ` Norbert Lange
2025-11-19 18:27 ` James Hilliard
2025-11-19 18:18 ` James Hilliard
2025-11-19 16:47 ` Marcus Hoffmann via buildroot
2025-11-19 17:02 ` James Hilliard
2026-01-01 22:09 ` Thomas Petazzoni via buildroot [this message]
2026-01-01 22:30 ` James Hilliard
2026-01-05 22:01 ` Norbert Lange
2026-01-06 9:39 ` Thomas Petazzoni via buildroot
2026-01-06 17:47 ` James Hilliard
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=20260101230904.6d78e9f5@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@bubu1.eu \
--cc=james.hilliard1@gmail.com \
--cc=nolange79@gmail.com \
--cc=sen@hastings.org \
--cc=thomas.petazzoni@bootlin.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