All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Ziegler <br025@umbiko.net>
Cc: buildroot@buildroot.org, Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v2 02/11] package/mpd: remove duplicated dependencies from sub-options
Date: Sat, 15 Aug 2026 21:37:07 +0200	[thread overview]
Message-ID: <aoC_d9SXLJGYRqR4@windsurf> (raw)
In-Reply-To: <20260709110822.305873-3-br025@umbiko.net>

Hello Andreas,

Thanks for your patch!

On Thu, Jul 09, 2026 at 01:08:06PM +0200, Andreas Ziegler wrote:
> After various updates since version 0.20, most dependencies placing
> restrictions on sub-components are now superseded by restrictions placed on
> MPD itself. Example: io_uring needs kernel headers > 5.1; MPD needs kernel
> headers > 5.6.
> 
> Remove dependencies from sub-options if they are already imposed on MPD. 
> 
> Signed-off-by: Andreas Ziegler <br025@umbiko.net>

Actually the general policy in Buildroot is somewhat the opposite of
what you're proposing here, even though I admit our general policy may
not be applied anywhere.

The reasoning for this policy is that it is either to review/verify
when an option "select" another one, that all "depends on" have
properly been replicated. Yes, this means potentially some duplication
of "depends on" between the main package option and the sub-options,
but it also allows to ensure that if we remove/change one of those
"depends on" from the main package option, we don't forget to have it
on the sub-option.

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

  reply	other threads:[~2026-08-15 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 11:08 [Buildroot] [PATCH v2 00/11] add runtime test for mpd Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 01/11] package/mpd: install provided sample configuration file as mpd.conf Andreas Ziegler
2026-08-15 17:08   ` Thomas Petazzoni via buildroot
2026-07-09 11:08 ` [Buildroot] [PATCH v2 02/11] package/mpd: remove duplicated dependencies from sub-options Andreas Ziegler
2026-08-15 19:37   ` Thomas Petazzoni via buildroot [this message]
2026-07-09 11:08 ` [Buildroot] [PATCH v2 03/11] package/mpd: reorder config items based on order in meson_options.txt Andreas Ziegler
2026-08-15 19:38   ` Thomas Petazzoni via buildroot
2026-07-09 11:08 ` [Buildroot] [PATCH v2 04/11] support/testing: add test data for mpd (1/6) Andreas Ziegler
2026-08-15 19:41   ` Thomas Petazzoni via buildroot
2026-07-09 11:08 ` [Buildroot] [PATCH v2 05/11] support/testing: add test data for mpd (2/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 06/11] support/testing: add test data for mpd (3/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 07/11] support/testing: add test data for mpd (4/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 08/11] support/testing: add test data for mpd (5/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 09/11] support/testing: add test data for mpd (6/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 10/11] support/testing: add runtime test for mpd Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 11/11] DEVELOPERS: add entry for test_mpd Andreas Ziegler
2026-07-11 10:24 ` [Buildroot] [PATCH v2 00/11] add runtime test for mpd Fiona Klute via buildroot
2026-07-12  2:54   ` Andreas Ziegler

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=aoC_d9SXLJGYRqR4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=br025@umbiko.net \
    --cc=buildroot@bubu1.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.