All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mpd: add mms support
Date: Mon, 9 Apr 2018 11:15:15 +0200	[thread overview]
Message-ID: <20180409111515.7669d88c@windsurf> (raw)
In-Reply-To: <20180407115230.22559-1-fontaine.fabrice@gmail.com>

Hello,

On Sat,  7 Apr 2018 13:52:30 +0200, Fabrice Fontaine wrote:
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  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

  reply	other threads:[~2018-04-09  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 11:52 [Buildroot] [PATCH 1/1] mpd: add mms support Fabrice Fontaine
2018-04-09  9:15 ` Thomas Petazzoni [this message]
2018-04-17 17:25   ` Fabrice Fontaine
2018-04-28 16:36 ` Thomas Petazzoni

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=20180409111515.7669d88c@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.