From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, marinus.savoritias@tuta.io
Cc: help-guix@gnu.org
Subject: Re: Kdenlive License follow-up.
Date: Wed, 18 Sep 2019 20:41:03 -0600 [thread overview]
Message-ID: <d605399e8dad597ad13b54df1c3eddb082fe8871.camel@gmail.com> (raw)
In-Reply-To: <87muf1o0ki.fsf@elephly.net>
On Wed, 2019-09-18 at 21:40 +0200, Ricardo Wurmus wrote:
> Hi Fanis,
>
> > I asked on the KDE matrix server regarding the Kdenlive licensing and
> > turns out they use GPL-3 in OpenSUSE. Most files are either GPL-2 or
> > GPL-3 or later + KDE Ev. clause so the package can't be licensed as
> > GPL-2 like Gentoo or GPL-2+ as in Guix.
>
> Thank you for the information.
>
> If you could point us to a file that is licensed under GPL version 3 or
> later we should change the license in the package definition to (list
> license:gpl2+ license:gpl3+) with a comment to state that the package is
> effectively under GPL version 3 or later.
>
> > As far as I know if a package has some GPL-3 files then it becomes
> > GPL-3 as a whole is that correct?
>
> Not necessarily. If it combines files under GPLv2 (only) with files
> that are under GPLv3 (only) then the project as a whole has conflicting
> licensing terms. That’s why the “or later” clause is really important.
> Software containing files under GPLv2+ and GPLv3 (only) would have an
> effective license of GPLv3 (only), while the individual files still
> retain their own terms.
>
> --
> Ricardo
>
>
gpl-3+
https://cgit.kde.org/kdenlive.git/tree/src/core.cpp
gpl-2+
https://cgit.kde.org/kdenlive.git/tree/src/capture/mltdevicecapture.cpp
next prev parent reply other threads:[~2019-09-19 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 19:12 Kdenlive License follow-up marinus.savoritias
2019-09-18 19:40 ` Ricardo Wurmus
2019-09-19 2:41 ` Jesse Gibbons [this message]
2019-09-21 7:06 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d605399e8dad597ad13b54df1c3eddb082fe8871.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=help-guix@gnu.org \
--cc=marinus.savoritias@tuta.io \
--cc=rekado@elephly.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).