From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/6] gmp: correct legal info
Date: Mon, 4 Jul 2016 18:07:07 +0200 [thread overview]
Message-ID: <20160704160707.GE3549@free.fr> (raw)
In-Reply-To: <1467636386-6759-5-git-send-email-rahul.bedarkar@imgtec.com>
Rahul, All,
On 2016-07-04 18:16 +0530, Rahul Bedarkar spake thusly:
> Since version 6, GMP is distributed under the dual licenses LGPLv3+ or
> GPLv2+
>
> Reviewed-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
> ---
> package/gmp/gmp.mk | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/gmp/gmp.mk b/package/gmp/gmp.mk
> index cdde794..485bf7c 100644
> --- a/package/gmp/gmp.mk
> +++ b/package/gmp/gmp.mk
> @@ -8,8 +8,8 @@ GMP_VERSION = 6.1.1
> GMP_SITE = $(BR2_GNU_MIRROR)/gmp
> GMP_SOURCE = gmp-$(GMP_VERSION).tar.xz
> GMP_INSTALL_STAGING = YES
> -GMP_LICENSE = LGPLv3+
> -GMP_LICENSE_FILES = COPYING.LESSERv3
> +GMP_LICENSE = LGPLv3+ or GPLv2+
> +GMP_LICENSE_FILES = COPYING.LESSERv3 COPYINGv2
There are also COPYING and COPYINGv3; both contain the text of the
GPLv3. I'm not sure whether we should carry them or not...
I've looked at a few files, used a few grep-fuu, and they seem to really
consistently refer to either LGPLv3 or GPLv2, which is what you wrote.
So I'd be tempted to agree with you.
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> GMP_DEPENDENCIES = host-m4
> HOST_GMP_DEPENDENCIES = host-m4
>
> --
> 2.6.2
>
> _______________________________________________
> 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:[~2016-07-04 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 12:46 [Buildroot] [PATCH 1/6] gnutls: update legal info Rahul Bedarkar
2016-07-04 12:46 ` [Buildroot] [PATCH 2/6] libuci: " Rahul Bedarkar
2016-07-04 15:46 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 3/6] dbus: " Rahul Bedarkar
2016-07-04 12:46 ` [Buildroot] [PATCH 4/6] iw: correct license name Rahul Bedarkar
2016-07-04 15:56 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 5/6] gmp: correct legal info Rahul Bedarkar
2016-07-04 16:07 ` Yann E. MORIN [this message]
2016-07-04 12:46 ` [Buildroot] [PATCH 6/6] alsa-lib: update " Rahul Bedarkar
2016-07-04 16:14 ` Yann E. MORIN
2016-07-05 7:15 ` Thomas Petazzoni
2016-07-04 15:39 ` [Buildroot] [PATCH 1/6] gnutls: " Yann E. MORIN
2016-07-04 22:13 ` Thomas Petazzoni
2016-07-04 22:14 ` 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=20160704160707.GE3549@free.fr \
--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