unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Mathieu <matf@disr.it>
Cc: 57744@debbugs.gnu.org
Subject: [bug#57744] [PATCH v2 2/3] gnu: Add shirah.
Date: Thu, 15 Sep 2022 22:17:07 +0200	[thread overview]
Message-ID: <c30d1a8c-105b-c593-2326-05406b68598e@telenet.be> (raw)
In-Reply-To: <1328a67f-525d-4c66-b38e-c6146a13c71f@disroot.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1939 bytes --]



On 15-09-2022 22:03, Mathieu wrote:
> Should I not use what they have in the LICENSE at the root of their repository instead?

shirah_reader does not have a LICENSE file, AFAICS.

Even if it did, usually the LICENSE file only contains the license text, 
and not extras like 'which version range'.

Even if there was a LICENSE file that states 'this version only', then 
there is still another file that states 'this version or later', then 
how would we know which one is correct?  Why would LICENSE have 
precedence?  Or why would the source file have precedence?

When such situations happen, we cannot resolve them, only the author can 
clarify matters.

Even if there is only a LICENSE file, then usually it does not specify 
‘this version only’ or ‘this version or later’.  In case of the GPL, we 
then have the following license condition:

‘14. Revised Versions of this License

Each version is given a distinguishing version number.  If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation.  _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._’

I don't consider adding a LICENSE file as ‘specifying a version number’, 
so I'd say that in such cases it's gpl1+ (as the license text needs to 
be distributed along the source code anyway (at least in v2 and v3)). 
(However, I suppose it could be argued that in such cases it's 
implicitly specified that it's ‘version-of-the-LICENSE-file-or-later’. 
Also not a lawyer.  And in such situations, maybe it would be best to 
just ask the author what they meant.)

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-09-15 20:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12  0:09 [bug#57744] [PATCH 0/3] Add shirah and dependencies M
2022-09-12  0:10 ` [bug#57744] [PATCH 1/3] gnu: Add python-ebooklib M
2022-09-12  0:10   ` [bug#57744] [PATCH 2/3] gnu: Add python-syllables M
2022-09-12  0:10   ` [bug#57744] [PATCH 3/3] gnu: Add shirah M
2022-09-14  8:09 ` [bug#57744] [PATCH 0/3] Add shirah and dependencies Christopher Baines
2022-09-15 19:57   ` Mathieu
2022-09-15 19:59     ` Maxime Devos
2022-09-15 19:58 ` [bug#57744] [PATCH v2 1/3] gnu: Add shirah M
2022-09-15 19:58   ` [bug#57744] [PATCH v2 2/3] " M
2022-09-15 20:01     ` Maxime Devos
2022-09-15 20:03       ` Mathieu
2022-09-15 20:17         ` Maxime Devos [this message]
2022-09-15 19:58   ` [bug#57744] [PATCH v2 3/3] gnu: Add python-syllables M
2022-09-15 20:38 ` [bug#57744] [PATCH v3 1/3] gnu: Add python-ebooklib M
2022-09-15 20:38   ` [bug#57744] [PATCH v3 2/3] gnu: Add python-syllables M
2022-09-15 20:38   ` [bug#57744] [PATCH v3 3/3] gnu: Add shirah M
2022-09-15 20:41     ` Mathieu
2022-09-16 10:43       ` bug#57744: " Christopher Baines

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=c30d1a8c-105b-c593-2326-05406b68598e@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=57744@debbugs.gnu.org \
    --cc=matf@disr.it \
    /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).