All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtasn1: clarify licensing info
Date: Thu, 29 Sep 2016 18:53:20 +0530	[thread overview]
Message-ID: <57ED15C8.5040805@imgtec.com> (raw)
In-Reply-To: <1475111638-24640-1-git-send-email-gustavo.zacarias@free-electrons.com>

Hi,

On Thursday 29 September 2016 06:43 AM, 
gustavo.zacarias at free-electrons.com wrote:
> From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
>
> The library is LGPLv2.1+, the tests and tools are GPLv3+ so clarify to
> avoid confusion.
>
> Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
> ---
>   package/libtasn1/libtasn1.mk | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/libtasn1/libtasn1.mk b/package/libtasn1/libtasn1.mk
> index 6b7e6b3..79223a4 100644
> --- a/package/libtasn1/libtasn1.mk
> +++ b/package/libtasn1/libtasn1.mk
> @@ -7,7 +7,7 @@
>   LIBTASN1_VERSION = 4.9
>   LIBTASN1_SITE = http://ftp.gnu.org/gnu/libtasn1
>   LIBTASN1_DEPENDENCIES = host-bison
> -LIBTASN1_LICENSE = GPLv3+, LGPLv2.1+
> +LIBTASN1_LICENSE = GPLv3+ (tests, tools), LGPLv2.1+ (library)

examples are also licensed under GPLv3+. But I'm not sure if we should 
add both tests and examples here when those don't go on target file system.

Apart form that

Reviewed-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>

Regards,
Rahul

  reply	other threads:[~2016-09-29 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29  1:13 [Buildroot] [PATCH] libtasn1: clarify licensing info gustavo.zacarias at free-electrons.com
2016-09-29 13:23 ` Rahul Bedarkar [this message]
2016-10-22 14:45 ` 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=57ED15C8.5040805@imgtec.com \
    --to=rahul.bedarkar@imgtec.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.