From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH] gnu: Add gnushogi and xshogi
Date: Thu, 23 Feb 2017 12:06:17 -0500 [thread overview]
Message-ID: <20170223170617.GB12804@jasmine> (raw)
In-Reply-To: <20170223051919.GA14149@jocasta.intra>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
On Thu, Feb 23, 2017 at 06:19:19AM +0100, John Darrington wrote:
> On Wed, Feb 22, 2017 at 04:58:07PM -0500, Leo Famulari wrote:
> On Wed, Feb 22, 2017 at 08:15:04PM +0100, John Darrington wrote:
> > * gnu/packages/games.scm (gnushogi, xshogi): New variables.
>
> > +(define-public xshogi
>
> [...]
>
> > + ;; Contains a copy of GPLv3 but the licence notices simply
> > + ;; state "GNU General Public Licence" without specifying a version.
> > + (license license:gpl1+)))
>
> Section 14 of the GPL says "If the Program does not specify a
> version number of the GNU General Public License, you may choose any
> version ever published by the Free Software Foundation."
>
> You are correct. That is why I put gpl1+
>
> Do we want to use version 1 of the GPL? I don't fully understand the
> issues with it, but it's an unusual choice.
>
> I don't have a strong opinion here. But there is a precedent in Guix, that
> where upstream permits a package to be distributed under a choice of licences,
> we simply present that choice to our users. We don't - at least I haven't seen
> any instances of it - choose a particular one that suits us, unless there is a
> good reason for doing that.
Okay, that makes sense to me. Please do as you see fit :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-02-23 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 19:15 [PATCH] gnu: Add gnushogi and xshogi John Darrington
2017-02-22 21:58 ` Leo Famulari
2017-02-23 5:19 ` John Darrington
2017-02-23 17:06 ` Leo Famulari [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=20170223170617.GB12804@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).