From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] gst1-plugins-bad: rework license type construction
Date: Sun, 13 May 2018 23:04:39 +0200 [thread overview]
Message-ID: <20180513210439.GP22130@scaer> (raw)
In-Reply-To: <1525633443-942-1-git-send-email-danomimanchego123@gmail.com>
Danomi, All,
On 2018-05-06 15:04 -0400, Danomi Manchego spake thusly:
> Use "GST1_PLUGINS_BAD_LICENSE := $(GST1_PLUGINS_BAD_LICENSE), xxxx" construct
> so that the list of licenses is presented as a comma-separated list.
>
> Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> ---
> package/gstreamer1/gst1-plugins-bad/gst1-plugins-bad.mk | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/gstreamer1/gst1-plugins-bad/gst1-plugins-bad.mk b/package/gstreamer1/gst1-plugins-bad/gst1-plugins-bad.mk
> index 9f7cd97..b001c33 100644
> --- a/package/gstreamer1/gst1-plugins-bad/gst1-plugins-bad.mk
> +++ b/package/gstreamer1/gst1-plugins-bad/gst1-plugins-bad.mk
> @@ -11,7 +11,7 @@ GST1_PLUGINS_BAD_INSTALL_STAGING = YES
> # Unknown and GPL licensed plugins will append to GST1_PLUGINS_BAD_LICENSE and
> # GST1_PLUGINS_BAD_LICENSE_FILES if enabled.
> GST1_PLUGINS_BAD_LICENSE_FILES = COPYING.LIB
> -GST1_PLUGINS_BAD_LICENSE = LGPL-2.0+, LGPL-2.1+
> +GST1_PLUGINS_BAD_LICENSE := LGPL-2.0+, LGPL-2.1+
>
> GST1_PLUGINS_BAD_CONF_OPTS = \
> --disable-examples \
> @@ -771,13 +771,13 @@ endif
>
> # Add GPL license if GPL licensed plugins enabled.
> ifeq ($(GST1_PLUGINS_BAD_HAS_GPL_LICENSE),y)
> -GST1_PLUGINS_BAD_LICENSE += GPL
> +GST1_PLUGINS_BAD_LICENSE := $(GST1_PLUGINS_BAD_LICENSE), GPL
> GST1_PLUGINS_BAD_LICENSE_FILES += COPYING
> endif
>
> # Add Unknown license if Unknown licensed plugins enabled.
> ifeq ($(GST1_PLUGINS_BAD_HAS_UNKNOWN_LICENSE),y)
> -GST1_PLUGINS_BAD_LICENSE += UNKNOWN
> +GST1_PLUGINS_BAD_LICENSE := $(GST1_PLUGINS_BAD_LICENSE), UNKNOWN
> endif
>
> # Use the following command to extract license info for plugins.
> --
> 2.7.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-05-13 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 19:04 [Buildroot] [PATCH 1/2] gst1-plugins-bad: rework license type construction Danomi Manchego
2018-05-06 19:04 ` [Buildroot] [PATCH 2/2] gst1-plugins-bad: update plugin licenses Danomi Manchego
2018-05-13 21:07 ` Yann E. MORIN
2018-05-24 21:02 ` Peter Korsgaard
2018-05-13 21:04 ` Yann E. MORIN [this message]
2018-05-13 21:22 ` [Buildroot] [PATCH 1/2] gst1-plugins-bad: rework license type construction Thomas Petazzoni
2018-05-14 2:01 ` Danomi Manchego
2018-05-14 6:10 ` Thomas Petazzoni
2018-05-24 21:02 ` Peter Korsgaard
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=20180513210439.GP22130@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox