All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Wolfgang Denk <wd@denx.de>
Cc: yocto@yoctoproject.org
Subject: Re: LICENSE = "GPL" -- problem?
Date: Tue, 15 May 2012 16:47:42 -0400	[thread overview]
Message-ID: <4FB2C0EE.3070509@windriver.com> (raw)
In-Reply-To: <20120514201154.8A627202B34@gemini.denx.de>

On 12-05-14 04:11 PM, Wolfgang Denk wrote:
> Hi,
>
> we noticed warnings like "No generic license file exists for: GPL in
> any provider" for our own linux kernel recipe.  The cause wa the use
> of an entry
>
> 	LICENSE = "GPL"
>
> which whould read "GPLv2" instead of "GPL".  A scan detected that the
> same string "GPL" is used in a number of other recipes:
>
> bitbake/lib/bb/shell.py:LICENSE = "GPL"
> meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:LICENSE = "GPL"

I've updated this license to be more specific. I'm not sure if a bug
was opened for the other ones, but I took care of the one that I
look after.

Cheers,

Bruce

> meta/recipes-kernel/linux/linux-dummy.bb:LICENSE = "GPL"
> meta/recipes-bsp/x-load/x-load.inc:LICENSE = "GPL"
> meta/recipes-devtools/gcc/gcc-common.inc:LICENSE = "GPL"
> meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb:LICENSE = "GPL"
>
> Eventually these should be fixed, too?
>
> Best regards,
>
> Wolfgang Denk
>



      parent reply	other threads:[~2012-05-15 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 20:11 LICENSE = "GPL" -- problem? Wolfgang Denk
2012-05-14 20:58 ` Flanagan, Elizabeth
2012-05-14 21:12   ` Wolfgang Denk
2012-05-15 20:47 ` Bruce Ashfield [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=4FB2C0EE.3070509@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=wd@denx.de \
    --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.