From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Fiona Klute <fiona.klute@gmx.de>,
Fiona Klute via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/2] docs/manual: describe relying on default options
Date: Tue, 9 Jul 2024 13:57:17 +0200 [thread overview]
Message-ID: <20240709135717.6f0f69d0@windsurf> (raw)
In-Reply-To: <a11a2bc2-cc24-421d-8333-2f0b622368b4@mind.be>
On Tue, 9 Jul 2024 12:13:08 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > I don't have a strong opinion, but I think
> > section https://buildroot.org/downloads/manual/manual.html#adding-packages-start-script
> > makes more sense, as it's actually close to where it matters. Arnout?
>
> The init scripts are just an example here, the principle applies more in
> general. It also applies to e.g. ifupdown scripts, or even systemd unit files
> (e.g. if a systemd unit file needs some ExecStartPre command). That's why I
> thought that the start script was not the most appropriate place.
ACK. But then perhaps the discussion can be extended beyond Busybox.
For example for uClibc-ng, we also assume it is built with our default
configuration, and don't try to support the myriad of possible
uClibc-ng configurations.
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:[~2024-07-09 11:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 9:44 [Buildroot] [PATCH 0/2] Manual updates Fiona Klute via buildroot
2024-07-05 9:44 ` [Buildroot] [PATCH 1/2] docs/manual: describe relying on default options Fiona Klute via buildroot
2024-07-08 21:11 ` Thomas Petazzoni via buildroot
2024-07-09 8:38 ` Fiona Klute via buildroot
2024-07-09 9:37 ` Thomas Petazzoni via buildroot
2024-07-09 10:13 ` Arnout Vandecappelle via buildroot
2024-07-09 11:57 ` Thomas Petazzoni via buildroot [this message]
2024-07-12 9:49 ` Fiona Klute via buildroot
2024-07-05 9:44 ` [Buildroot] [PATCH 2/2] docs/manual: allow sponsor mention in author name Fiona Klute via buildroot
2024-07-08 21:10 ` Thomas Petazzoni via buildroot
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=20240709135717.6f0f69d0@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=fiona.klute@gmx.de \
--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