guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#57744] [PATCH v2 2/3] gnu: Add shirah.


From: Maxime Devos
Subject: [bug#57744] [PATCH v2 2/3] gnu: Add shirah.
Date: Thu, 15 Sep 2022 22:17:07 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0



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: OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]