all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "ng0" <contact.ng0@cryptolab.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Fix the reducelcs license
Date: Wed, 01 Feb 2017 23:56:03 +0000	[thread overview]
Message-ID: <877f59zcrw.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87k299a731.fsf@gnu.org>


Ludovic Courtès writes:

> Kei Kebreau <kei@openmailbox.org> skribis:
>
>> contact.ng0@cryptolab.net writes:
>>
>>> If I am not wrong: When no "Version 3 only" is specified, it is always
>>> "and later".
>>
>> Is there text in the GPL3 that says this? I was under the impression
>> that the "or any later version" clause had to be specified
>> explicitly.
>
> No it’s the opposite.
>
> Specifically, from Section 14 of GPLv3:
>
>   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.
>
> In Guix we encode this as ‘gpl3+’.
>
> So the rule is: always put ‘+’ unless the source code headers or some
> other prominent file restricts to a specific version of the license.
>
> Ludo’.

Ah, thanks for the explanation. I will save this somewhere.

So the patch I've sent preceding this small discussion should
still be applied.
-- 
ng0 . https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-02-01 23:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 11:32 Fix the reducelcs license contact.ng0
2017-01-31 11:32 ` [PATCH] gnu: reducelcs: Correct license contact.ng0
2017-01-31 15:02 ` Fix the reducelcs license Kei Kebreau
2017-01-31 16:29   ` Marius Bakke
2017-01-31 17:38     ` ng0
2017-02-01 22:18   ` Ludovic Courtès
2017-02-01 23:56     ` ng0 [this message]
2017-02-02  0:54       ` Kei Kebreau
2017-02-02 10:39       ` Hartmut Goebel

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=877f59zcrw.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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 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.