From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH 1/2] docs/manual: describe relying on default options
Date: Mon, 8 Jul 2024 23:11:51 +0200 [thread overview]
Message-ID: <20240708231151.2606b9ff@windsurf> (raw)
In-Reply-To: <20240705094449.8550-2-fiona.klute@gmx.de>
On Fri, 5 Jul 2024 11:44:48 +0200
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> People can assume that e.g. Busybox options enabled in the package are
> enabled when writing code for Buildroot. Anyone who uses custom
> configurations that disable default options needs to make sure
> relevant scripts etc. still work for themselves.
>
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
> ---
> docs/manual/integration-principles.adoc | 18 ++++++++++++++++++
> docs/manual/integration.adoc | 2 ++
> 2 files changed, 20 insertions(+)
> create mode 100644 docs/manual/integration-principles.adoc
>
> diff --git a/docs/manual/integration-principles.adoc b/docs/manual/integration-principles.adoc
> new file mode 100644
> index 0000000000..9e2f43a18a
> --- /dev/null
> +++ b/docs/manual/integration-principles.adoc
> @@ -0,0 +1,18 @@
> +// -*- mode:doc; -*-
> +// vim: set syntax=asciidoc:
> +
> +[[integration-principles]]
> +=== Integration Principles
> +
> +Some foundational packages like Busybox can be configured with or
> +without certain features. When writing Buildroot code that uses such
> +packages, contributors may assume that the options enabled in the
> +Buildroot-provided configurations are enabled. For example,
> ++package/busybox/busybox.config+ sets
> ++CONFIG_FEATURE_START_STOP_DAEMON_LONG_OPTIONS=y+, so init scripts
> +meant for use with Busybox init may use +start-stop-daemon+ with long
> +form options.
> +
> +People who use custom configurations that disable such default options
> +are responsible for making sure that all relevant scripts still work,
> +and if not, adapting them accordingly (in an overlay).
I understand the wish to document this, but I'm not sure an
"Integration principles" is the right place. Shouldn't we document that
in a section where we document the expectations in terms of init
scripts instead?
Best regards,
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-08 21:12 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 [this message]
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
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=20240708231151.2606b9ff@windsurf \
--to=buildroot@buildroot.org \
--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