All of lore.kernel.org
 help / color / mirror / Atom feed
From: virendra kumar thakur <coolveer07@gmail.com>
To: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: /usr/share/common-license package/recipeinfo contains GPLv3 info
Date: Thu, 23 May 2019 15:12:59 +0530	[thread overview]
Message-ID: <CANGFfGYLEXR49NvsQUuDawFoGDYiDzGPVaqLiaN=vZzSbdtsnQ@mail.gmail.com> (raw)
In-Reply-To: <CANGFfGa=qMdrWzo-Lxs-tb=6q3XH7aqXVrOd7JdC3G9Yk3Lp=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

Hello team,

I am trying to build yocto image without GPLv3 package, I have added below
things in local.conf and enable meta-gplv2 layer.

INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" in local.conf.

After verifying from package.manifest and license.manifest file in
build/tmp/deploy/license/ directory I observe that no GPLv3 package is
present in rootfs.

But I can see in
rootfs/usr/share/common-license/package/libgcrypt-lic/recipeinfo

LICENSE: GPLV2+ &LGPLV2.1+ &GPLV3+
PR: r0
PV : 1.8.4

Is present..

My doubt is why any GPLv3 is present in common-license directory?

From: "Burton, Ross" <ross.burton@intel.com>
To: virendra kumar thakur <coolveer07@gmail.com>
Cc: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: [yocto] GPLv3 package present in rootfs

On Wed, 22 May 2019 at 06:26, virendra kumar thakur
<coolveer07@gmail.com> wrote:
> still some package gnutls, libidn2, libassuan, are added into rootfs.

Randomly picking libassuan:

LICENSE_${PN} = "LGPLv2.1+"

The library itself is LGPL-2.  Have you verified the *package*
licenses for what is actually going into the image?

Ross

[-- Attachment #2: Type: text/html, Size: 4692 bytes --]

       reply	other threads:[~2019-05-23  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANGFfGa=qMdrWzo-Lxs-tb=6q3XH7aqXVrOd7JdC3G9Yk3Lp=g@mail.gmail.com>
2019-05-23  9:42 ` virendra kumar thakur [this message]
2019-05-23 23:55   ` /usr/share/common-license package/recipeinfo contains GPLv3 info Khem Raj
2019-05-24  6:37     ` virendra kumar thakur
2019-05-24  8:42   ` Burton, Ross
2019-05-24  8:53     ` virendra kumar thakur

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='CANGFfGYLEXR49NvsQUuDawFoGDYiDzGPVaqLiaN=vZzSbdtsnQ@mail.gmail.com' \
    --to=coolveer07@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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.