From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Andreas Ziegler <br015@umbiko.net>
Cc: "Jörg Krause" <joerg.krause@embedded.rocks>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/mpd: update to version 0.23.2
Date: Sun, 14 Nov 2021 16:08:03 +0100 [thread overview]
Message-ID: <20211114160803.5ce09ba5@windsurf> (raw)
In-Reply-To: <20211025094453.245364-1-br015@umbiko.net>
Hello Andreas,
Thanks for this patch. I have some comments below, but more
importantly, I would really like to get the review/approval from Jörg
Krause on this patch, as he has usually been maintaining this package.
On Mon, 25 Oct 2021 11:44:53 +0200
Andreas Ziegler <br015@umbiko.net> wrote:
> In addition to various bug fixes, mpd version 0.23 introduces a new
> dependency (mft) and a change in the configuration of the UPnP client
> functionality.
>
> Optional new features (openmpt decoder, pipewire and snapcast outputs) are
> currently not available as Buildroot packages and were not considered.
We do have pipewire as a package in Buildroot, so that aspect doesn't
seem completely true. If you don't handle those dependencies in mpd.mk
(which is fine), could you disable them explicitly by passing the
appropriate -Dfoo=disabled, if available?
> The change log can be found in [1]
>
> Introduce new dependency for fmt library. Change configuration of UPnP plugin
> to submenu, allowing to optionally select libupnp, libnpupnp or disabled. The
> default setting is 'no UPnP client functionality'. Correct a typo in toolchain
> dependency comment. Adapt sparc patch to changes in source layout.
The typo in the toolchain dependency comment should be addressed in a
separate patch, as it is really an unrelated bug fix.
> diff --git a/package/mpd/Config.in b/package/mpd/Config.in
> index 7a2597558b..7b5aeb4bf6 100644
> --- a/package/mpd/Config.in
> +++ b/package/mpd/Config.in
> @@ -8,6 +8,7 @@ menuconfig BR2_PACKAGE_MPD
> depends on BR2_TOOLCHAIN_GCC_AT_LEAST_8 # C++17
> depends on BR2_HOST_GCC_AT_LEAST_8 # C++17
> select BR2_PACKAGE_BOOST
> + select BR2_PACKAGE_FMT
You're adding this here, but it's not added in MPD_DEPENDENCIES. Is fmt
a build-time or a run-time dependency?
You can check this by doing "make clean && make mpd" and verify that it
does build.
> select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
> help
> MPD is a flexible, powerful, server-side application
> @@ -361,7 +362,7 @@ config BR2_PACKAGE_MPD_LIBMPDCLIENT
>
> config BR2_PACKAGE_MPD_NEIGHBOR_DISCOVERY_SUPPORT
> bool "neighbor discovery support"
> - depends on BR2_PACKAGE_MPD_LIBSMBCLIENT || BR2_PACKAGE_MPD_UPNP
> + depends on BR2_PACKAGE_MPD_LIBSMBCLIENT || !BR2_PACKAGE_MPD_UPNP_DISABLED
> help
> Enable support for neighbor discovery.
> This option can be used in conjunction with the smbclient
> @@ -380,13 +381,39 @@ config BR2_PACKAGE_MPD_TCP
> You want this on if MPD and the client(s) work
> on different machines (the usual scenario).
>
> -config BR2_PACKAGE_MPD_UPNP
> - bool "UPnP"
> +choice
Kind of annoying to have a "choice" here. Is there a good reason to
support both uPNP implementations?
> + prompt "UPnP"
> + default BR2_PACKAGE_MPD_UPNP_DISABLED
> + help
> + Enable MPD UPnP client support.
> +
> +config BR2_PACKAGE_MPD_UPNP_PUPNP
> + bool "pupnp"
> select BR2_PACKAGE_EXPAT
> select BR2_PACKAGE_LIBUPNP
> select BR2_PACKAGE_MPD_CURL
> help
> - Enable MPD UPnP client support.
> + Provides UPnP functionality through libupnp
> + (the legacy Portable SDK for UPnP devices).
> +
> + Introduces least additional dependencies.
> +
> +config BR2_PACKAGE_MPD_UPNP_NPUPNP
> + bool "npupnp"
> + select BR2_PACKAGE_LIBNPUPNP
> + select BR2_PACKAGE_MPD_CURL
> + help
> + Provides UPnP functionality through libnpupnp
> + (a C++ reimplementation of the Portable UPnP library).
> +
> + Prefer this option if you plan to use upmpdcli.
> +
> +config BR2_PACKAGE_MPD_UPNP_DISABLED
I think I would prefer BR2_PACKAGE_MPD_UPNP_NONE.
Thanks a lot!
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:[~2021-11-14 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 9:44 [Buildroot] [PATCH 1/1] package/mpd: update to version 0.23.2 Andreas Ziegler
2021-11-14 15:08 ` Thomas Petazzoni [this message]
2021-11-15 9:04 ` Andreas Ziegler
2021-11-15 12:32 ` [Buildroot] [PATCH v2 0/2] package/mpd: update to version 0.23.y Andreas Ziegler
2021-11-15 12:32 ` [Buildroot] [PATCH v2 1/2] package/mpd: correct typo in help message Andreas Ziegler
2021-12-10 19:02 ` Arnout Vandecappelle
2021-11-15 12:32 ` [Buildroot] [PATCH v2 2/2] package/mpd: update to version 0.23.y Andreas Ziegler
2021-12-10 19:07 ` Arnout Vandecappelle
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=20211114160803.5ce09ba5@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=br015@umbiko.net \
--cc=buildroot@buildroot.org \
--cc=joerg.krause@embedded.rocks \
/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