From: Jesse Gibbons <jgibbons2357@gmail.com>
To: marinus.savoritias@tuta.io, help-guix@gnu.org
Subject: Re: Question about Licenses.
Date: Sun, 15 Sep 2019 13:06:15 -0600 [thread overview]
Message-ID: <d7642d9f9e57aed1ac801ea8438b02f540fa594b.camel@gmail.com> (raw)
In-Reply-To: <Lopbqhp--3-1@tuta.io>
Hi Marinus,
On Sun, 2019-09-15 at 17:51 +0200, marinus.savoritias@tuta.io wrote:
> Hi Everyone.
>
> My name is Fanis and I am a new Guix user coming from Gentoo. I am
> very interested in the license around the packages I use and I can
> help but notice some inconsistencies.
> For example:
> kdenlive is GPL-2 in the gentoo repositories.
> https://packages.gentoo.org/packages/kde-apps/kdenlive <https://packa
> ges.gentoo.org/packages/kde-apps/kdenlive>
> It also has a link to GPL-2 on their site:
> https://kdenlive.org/en/about/ <https://kdenlive.org/en/about/>
> But on Guix is GPL-2+.
>
> Is there a source I am not considering? The source is saying GPL-2 in
> the copying file too.
Just browsing the kdenlive cgit...
https://cgit.kde.org/kdenlive.git/tree/src/core.cpp
kdenlive has some GPL-3+ code in its repository.
https://cgit.kde.org/kdenlive.git/tree/src/capture/mltdevicecapture.cpp
kdenlive has some GPL-2+ code in its repository.
The license in the package definition should be a list including GPL-2+
and GPL-3+, and the kdenlive maintainers should update the README
file.
I usually search source for "(at your option)" (outside /COPYING
because the string is in the GNU licenses) to determine the license
specifics.
>
> Regards,
> Fanis
--
-Jesse
prev parent reply other threads:[~2019-09-15 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 15:51 Question about Licenses marinus.savoritias
2019-09-15 17:15 ` Ricardo Wurmus
2019-09-15 18:42 ` marinus.savoritias
2019-09-15 19:06 ` Jesse Gibbons [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
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=d7642d9f9e57aed1ac801ea8438b02f540fa594b.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=help-guix@gnu.org \
--cc=marinus.savoritias@tuta.io \
/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).