From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH] geany-plugins: include GPLv3 in the main LICENSE
Date: Mon, 29 Aug 2016 22:52:53 +0200 [thread overview]
Message-ID: <20160829205253.17988-1-Martin.Jansa@gmail.com> (raw)
* since last changes in oe-core LICENSE variable needs to list all licenses used
by individual packages otherwise bitbake warning like this is shown:
WARNING: meta-openembedded/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb: LICENSE_geany-plugins-commander includes licenses (GPLv3) that are not listed in LICENSE
as possible improvement you can set LICENSE to GPLv2 to all plugins
which are GPLv2-only, because now they will "inherit" both GPLv2 &
GPLv3 which sucks as described here:
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg81645.html
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb b/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb
index 9a39150..5e1e721 100644
--- a/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb
+++ b/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb
@@ -1,7 +1,7 @@
DESCRIPTION = "A fast and lightweight IDE"
HOMEPAGE = "http://plugins.geany.org/"
# majority's default
-LICENSE = "GPLv2"
+LICENSE = "GPLv2 & GPLv3"
DEPENDS = "geany lua libxml2 libsoup-2.4 vte enchant intltool-native libassuan gpgme"
--
2.9.2
next reply other threads:[~2016-08-29 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 20:52 Martin Jansa [this message]
2016-08-30 1:02 ` [meta-oe][PATCH] geany-plugins: include GPLv3 in the main LICENSE Christopher Larson
2016-08-30 8:11 ` Martin Jansa
2016-08-30 8:24 ` Andreas Müller
2016-08-30 8:28 ` Martin Jansa
2016-08-30 8:33 ` Andreas Müller
2016-08-30 8:39 ` André Draszik
2016-08-30 8:41 ` Andreas Müller
2016-08-31 14:35 ` Martin Jansa
2016-08-31 14:59 ` Andreas Müller
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=20160829205253.17988-1-Martin.Jansa@gmail.com \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.