From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: Help identifying licenses
Date: Sun, 06 Oct 2019 20:56:24 +0200 [thread overview]
Message-ID: <875zl1ln3b.fsf@nckx> (raw)
In-Reply-To: <644c16fbe6b0151174a3a91e67c1dba092bfa778.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
Jesse,
Jesse Gibbons 写道:
> 1. newspeak
> The author says bsd-like. I don't see any clauses or
> yelling. What should I
> put for it? Here's the relevant snippet from debian/copyright:
This is the ‘Expat’ licence, often ambiguously called ‘MIT’.
> 2. Kenny
> The author says Artistic as found on debian in
> /usr/share/common-
> licenses/Artistic. It is not found in (guix licenses), and
> sincee I do not
> run debian from that era I cannot compare the text to verify the
> license's
> identity. Here's the relevant snippet from debian/copyright:
As noted on IRC: I've mirrored that file from a debian system[0].
What a mess: it's *almost*
<https://directory.fsf.org/wiki/License:Clarified_Artistic_License_1.0>,
but not actually the same (e.g. points 3.e & 4.e are missing).
Considering this is what Debian calls the ‘Artistic’ licence,
though, we can be almost certain that other Guix packages have the
same subtle difference already.
Kind regards,
T G-R
[0]: https://www.tobias.gr/Debian.Artistic.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-10-06 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 17:55 Help identifying licenses Jesse Gibbons
2019-10-06 18:56 ` Tobias Geerinckx-Rice [this message]
2019-10-06 18:58 ` Tobias Geerinckx-Rice
2019-10-06 19:59 ` Jesse Gibbons
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=875zl1ln3b.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@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.
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).