From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 9 Apr 2018 11:15:15 +0200 Subject: [Buildroot] [PATCH 1/1] mpd: add mms support In-Reply-To: <20180407115230.22559-1-fontaine.fabrice@gmail.com> References: <20180407115230.22559-1-fontaine.fabrice@gmail.com> Message-ID: <20180409111515.7669d88c@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Sat, 7 Apr 2018 13:52:30 +0200, Fabrice Fontaine wrote: > Signed-off-by: Fabrice Fontaine > --- > package/mpd/Config.in | 6 ++++++ > package/mpd/mpd.mk | 7 +++++++ > 2 files changed, 13 insertions(+) > > diff --git a/package/mpd/Config.in b/package/mpd/Config.in > index 6c7468e173..831e4ab0d7 100644 > --- a/package/mpd/Config.in > +++ b/package/mpd/Config.in > @@ -180,6 +180,12 @@ config BR2_PACKAGE_MPD_CURL > help > Enable curl streaming (http) support. > > +config BR2_PACKAGE_MPD_LIBMMS > + bool "mms" > + select BR2_PACKAGE_LIBMMS > + help > + Enable MMS support. Shouldn't we propagate the dependencies of the libmms package ? I suppose most (all ?) of them are already covered by the BR2_PACKAGE_MPD option, but shouldn't we propagate them anyway, in case we change the dependencies of BR2_PACKAGE_MPD in the future ? Do we a clear policy on this ? Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com