From: Marius Bakke <mbakke@fastmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, guix-devel@gnu.org
Subject: Re: [PATCH 1/7] gnu: Add KDE frameworkintegration.
Date: Mon, 21 Nov 2016 19:20:32 +0100 [thread overview]
Message-ID: <87twb07kzz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <58333672.4060804@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Am 21.11.2016 um 18:25 schrieb Marius Bakke:
>>> > + (license (list license:gpl2+ license:lgpl2.0 license:lgpl2.0+))))
>> Please clarify. Is it all of them, or either? Or is it mostly gpl2+, but
>> some files are covered by the other two?
>
> Thansk for reviewing that quick.
>
> The list of licenses is taken from Debian, which has a detailed lists of
> all the licenses used in each package. And KDE often has a *fast* number
> of different licenses in one package.
Thanks. Here is the Debian copyright file for this package:
http://metadata.ftp-master.debian.org/changelogs/main/f/frameworkintegration/frameworkintegration_5.28.0-1_copyright
Reading that, it seems this package is mostly gpl2 *OR* gpl3, and that
KDE invokes section 14 [0] of the GPL to decide whether later versions
are allowed.
[0] https://www.gnu.org/licenses/gpl-3.0.html#section14
I wonder if we should seek a statement from KDE allowing the use of
GPL3+ for our packages.
Meanwhile, the way I read it, this package should be '(gpl2 gpl3 lpgl2.0
lgpl2.0+). I would change the comment to something like:
;; This is distributed under either gpl2 or gpl3, but some files are
;; covered by other licenses.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2016-11-21 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 16:11 [PATCH 0/7] KDE Framework: Tier 4 and porting aids Hartmut Goebel
2016-11-21 16:11 ` [PATCH 1/7] gnu: Add KDE frameworkintegration Hartmut Goebel
2016-11-21 17:25 ` Marius Bakke
2016-11-21 18:01 ` Hartmut Goebel
2016-11-21 18:20 ` Marius Bakke [this message]
2016-11-21 18:30 ` Marius Bakke
2016-11-21 16:11 ` [PATCH 2/7] gnu: Add kdelibs4support Hartmut Goebel
2016-11-21 17:40 ` Marius Bakke
2016-11-21 16:11 ` [PATCH 3/7] gnu: Add khtml Hartmut Goebel
2016-11-21 17:42 ` Marius Bakke
2016-11-21 16:11 ` [PATCH 4/7] gnu: Add kjs Hartmut Goebel
2016-11-21 17:44 ` Marius Bakke
2016-11-21 16:11 ` [PATCH 5/7] gnu: Add kjsembed Hartmut Goebel
2016-11-21 17:46 ` Marius Bakke
2016-11-21 16:11 ` [PATCH 6/7] gnu: Add kmediaplayer Hartmut Goebel
2016-11-21 17:47 ` Marius Bakke
2016-11-21 16:11 ` [PATCH 7/7] gnu: Add kross Hartmut Goebel
2016-11-21 17:50 ` Marius Bakke
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=87twb07kzz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.