From: Andreas Ziegler <br025@umbiko.net>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v2 03/11] package/mpd: reorder config items based on order in meson_options.txt
Date: Mon, 17 Aug 2026 03:40:07 +0000 [thread overview]
Message-ID: <d69442026a8c993fdd6e551fadfa7ca2@umbiko.net> (raw)
In-Reply-To: <aoC_7t65PJ5NLjlc@windsurf>
Hi Thomas, Everyone,
On 2026-08-15 19:38, Thomas Petazzoni wrote:
> Hello Andreas,
>
> On Thu, Jul 09, 2026 at 01:08:07PM +0200, Andreas Ziegler wrote:
>> MPD has 99 configurable options; of these, 44 are exposed in
>> Buildroot's
>> Config.in. Sort order and grouping of these options are different
>> within
>> the MPD project and Buildroot, which makes a comparison difficult.
>>
>> Reorder entries in Config.in to reflect their order in
>> meson_options.txt.
>> Also update at least some of the help texts to more closely resemble
>> what
>> is published in the MPD manual.
>
> Thanks for your patch.
>
> The Buildroot policy in terms of sorting options in Config.in is
> rather "alphabetic ordering" and not "whatever order is used in the
> upstream meson_options.txt or configure.ac".
The original order in the mpd Config.in was by functional groups. These
are indeed sorted alphabetical. Using the meson_options.txt order would
make comparisons much easier ...
> Note that it is very possible that alphabetic ordering is already
> broken, in which case it would be totally OK to fix. But we will
> prefer to keep alphabetic ordering vs. meson_options.txt
> ordering. This is most notably to have a consistent policy between all
> our packages.
I will leave the file as-is for now.
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
Kind regards,
Andreas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-17 3:40 UTC|newest]
Thread overview: 25+ 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-08-17 3:18 ` Andreas Ziegler
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
2026-08-17 3:27 ` Andreas Ziegler
2026-08-17 3:31 ` Andreas Ziegler
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-08-17 3:40 ` Andreas Ziegler [this message]
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-08-17 3:47 ` Andreas Ziegler
2026-08-17 6:59 ` Thomas Petazzoni via buildroot
2026-08-17 11:27 ` Andreas Ziegler
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=d69442026a8c993fdd6e551fadfa7ca2@umbiko.net \
--to=br025@umbiko.net \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.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 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.