From: Leo Famulari <leo@famulari.name>
To: Jookia <166291@gmail.com>
Cc: guix-devel@gnu.org, thylakoid@openmailbox.org
Subject: Re: [PATCH] gnu: Add pioneers
Date: Mon, 15 Feb 2016 21:17:35 -0500 [thread overview]
Message-ID: <20160216021735.GA11870@jasmine> (raw)
In-Reply-To: <20160216020334.GA3987@novena-choice-citizen.lan>
On Tue, Feb 16, 2016 at 01:03:34PM +1100, Jookia wrote:
> On Mon, Feb 15, 2016 at 08:21:04PM -0500, Leo Famulari wrote:
> > > + (home-page "http://pio.sourceforge.net/")
> > > + (license license:gpl2+)))
> >
> > Since the source files include the "any later version" clause, I changed
> > this to GPL3+. I usually grep for 'later version' when COPYING indicates
> > GPL2.
>
> I don't like this and I think this is a bad idea. The project isn't licensed
> under the GPLv3+, it's licensed under the GPLv2+. When people search for
> packages and read licenses they're not going to be misinformed. I feel this is a
> disservice to the users of Guix, and misleading at best or dishonest at worst.
>
> You mentioned in IRC that this is supposed to be for the package that Guix
> builds and distributes. Indeed, the Guix documentation says the license field is
> for "The license of the package", not the license of the software in the
> package. Yet the home-page field is "The URL to the home-page of the package",
> and the synopsis field is "A one-line description of the package." 'package'
> here means the upstream, not the Guix package. Logic says that the license is
> for the software, and yet it's being misrepresented.
>
> I'd much rather like a package manager that reliably tells me the license for
> upstream software, but I have a feeling this is a sore political spot. I don't
> even get why you'd distribute the package under a newer GPL- this makes packages
> that were previously compatible incompatible!
>
> I don't care for the politics, but I think at the very least the 'license' field
> needs to be explicitly documented as not the license for the upstream software.
>
> Jookia.
You're right, I was wrong. I'm correcting this mistake and looking
through my history to see if I've made it elsewhere.
next prev parent reply other threads:[~2016-02-16 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 21:14 [PATCH] gnu: Add pioneers thylakoid
2016-02-16 1:21 ` Leo Famulari
2016-02-16 2:03 ` Jookia
2016-02-16 2:17 ` Leo Famulari [this message]
2016-02-16 2:20 ` Mark H Weaver
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=20160216021735.GA11870@jasmine \
--to=leo@famulari.name \
--cc=166291@gmail.com \
--cc=guix-devel@gnu.org \
--cc=thylakoid@openmailbox.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).