From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] gstreamer: add legal info
Date: Wed, 18 Nov 2015 22:40:20 +0100 [thread overview]
Message-ID: <564CF044.4010002@mind.be> (raw)
In-Reply-To: <1447850352-26299-1-git-send-email-gustavo.zacarias@free-electrons.com>
On 18-11-15 13:39, gustavo.zacarias at free-electrons.com wrote:
> From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
>
> Even though COPYING is LGPLv2+ some code files state v2.1+
Correct.
>
> Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
> ---
> package/gstreamer/gstreamer/gstreamer.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/gstreamer/gstreamer/gstreamer.mk b/package/gstreamer/gstreamer/gstreamer.mk
> index 1dbd66f..156afab 100644
> --- a/package/gstreamer/gstreamer/gstreamer.mk
> +++ b/package/gstreamer/gstreamer/gstreamer.mk
> @@ -8,6 +8,8 @@ GSTREAMER_VERSION = 0.10.36
> GSTREAMER_SOURCE = gstreamer-$(GSTREAMER_VERSION).tar.xz
> GSTREAMER_SITE = http://gstreamer.freedesktop.org/src/gstreamer
> GSTREAMER_INSTALL_STAGING = YES
> +GSTREAMER_LICENSE = LGPLv2+ LGPLv2.1+
We separate these things by commas. Otherwise looks good so
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
I was thinking, why not simply claim it is LGPLv2.1+, given that it's + anyway?
The binaries will anyway need to be LGPLv2.1+ because there's always some 2.1
code in there. So I would actually propose
# Some files are LGPLv2+, but the whole will be 2.1+
GSTREAMER_LICENSE = LGPLv2.1+
# COPYING file is actually for v2
GSTREAMER_LICENSE_FILES = COPYING
Regards,
Arnout
> +GSTREAMER_LICENSE_FILES = COPYING
>
> # Checking if unaligned memory access works correctly cannot be done when cross
> # compiling. For the following architectures there is no information available
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-11-18 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 12:39 [Buildroot] [PATCH 1/6] gstreamer: add legal info gustavo.zacarias at free-electrons.com
2015-11-18 12:39 ` [Buildroot] [PATCH 2/6] gst-plugins-base: " gustavo.zacarias at free-electrons.com
2015-11-18 21:49 ` Arnout Vandecappelle
2015-11-18 12:39 ` [Buildroot] [PATCH 3/6] gst-plugins-good: " gustavo.zacarias at free-electrons.com
2015-11-18 21:53 ` Arnout Vandecappelle
2015-11-18 12:39 ` [Buildroot] [PATCH 4/6] gst-plugins-bad: " gustavo.zacarias at free-electrons.com
2015-11-18 22:03 ` Arnout Vandecappelle
2015-11-19 22:08 ` Gustavo Zacarias
2015-11-18 12:39 ` [Buildroot] [PATCH 5/6] gst-plugins-ugly: " gustavo.zacarias at free-electrons.com
2015-11-18 22:12 ` Arnout Vandecappelle
2015-11-19 22:06 ` Gustavo Zacarias
2015-11-20 21:27 ` Arnout Vandecappelle
2015-11-18 12:39 ` [Buildroot] [PATCH 6/6] gst-ffmpeg: " gustavo.zacarias at free-electrons.com
2015-11-18 22:15 ` Arnout Vandecappelle
2015-11-18 21:40 ` Arnout Vandecappelle [this message]
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=564CF044.4010002@mind.be \
--to=arnout@mind.be \
--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