From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH] package/kodi: propagate mariadb dependencies to BR2_PACKAGE_KODI_MYSQL
Date: Sun, 13 Sep 2026 17:56:30 +0200 [thread overview]
Message-ID: <aqbHfSXJn0fhmuvK@windsurf> (raw)
In-Reply-To: <031430f63fb15e3b24b3627fb14bc16d@free.fr>
On Sun, Sep 13, 2026 at 05:36:49PM +0200, Julien Olivain wrote:
> > We don't have a super clear/strong policy on whether dependencies need
> > to be replicated to a sub-option when the package top-level option
> > already has them. I haven't done so in this case, but if people feel
> > like it should be done, I'll be happy to send an updated patch.
>
> I think most packages are not replicating top-level options.
> When there is replication, it is sometime due to leftovers
> after changes. This is why I applied this patch.
The concern I have with not replicating is that then it's easy to miss
re-adding dependency to sub-options when dependencies get removed from
the top-level option for $whatever reason.
And of course the concern with replicating is that it adds a whole lot
more of Config.in comments :)
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
prev parent reply other threads:[~2026-09-13 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 12:07 [Buildroot] [PATCH] package/kodi: propagate mariadb dependencies to BR2_PACKAGE_KODI_MYSQL Thomas Petazzoni via buildroot
2026-09-13 15:36 ` Julien Olivain via buildroot
2026-09-13 15:56 ` Thomas Petazzoni via buildroot [this message]
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=aqbHfSXJn0fhmuvK@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
--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