From: Marius Bakke <mbakke@fastmail.com>
To: Vagrant Cascadian <vagrant@debian.org>, 31958@debbugs.gnu.org
Subject: [bug#31958] [PATCH] gnu: Add python-pyblake2.
Date: Mon, 25 Jun 2018 23:20:07 +0200 [thread overview]
Message-ID: <87h8lqzhq0.fsf@fastmail.com> (raw)
In-Reply-To: <878t72o9r4.fsf@aikidev.net>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Vagrant Cascadian <vagrant@debian.org> writes:
>>> + (license license:cc0)))
>>
>> According to COPYING, this software is actually "octuple-licensed":
>>
>> * CC0 Universal 1.0 - http://creativecommons.org/publicdomain/zero/1.0
>> * Unlicense — http://unlicense.org/
>> * WTFPL Version 2 - http://www.wtfpl.net/
>> * Apache Public License 2.0 - https://www.apache.org/licenses/LICENSE-2.0
>> * OpenSSL License - https://www.openssl.org/source/license.html
>> * MIT License - https://opensource.org/licenses/MIT
>> * The BSD 3-Clause License - https://opensource.org/licenses/BSD-3-Clause
>> * ISC License - https://opensource.org/licenses/ISC
>>
>> Can you add each of these, along with an explaning comment?
>
> And all of those are merely fallback licenses to the author's intention
> of public domain... and in the files themselves (pyblake2module.c,
> setup.py), they only reference:
>
> http://creativecommons.org/publicdomain/zero/1.0
>
> But if it's more appropriate for guix to list all possible licenses,
> sure. :)
Right. I missed the top comment of the COPYING file[0], which dedicates
the software to the public domain. But it also says that you are free
to choose any of the others at your discretion.
So I think CC0 is appropriate, but please add a comment explaning the
situation. Thanks!
[0] https://github.com/dchest/pyblake2/blob/master/COPYING
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-06-25 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 20:06 [bug#31958] [PATCH] gnu: Add python-pyblake2 Vagrant Cascadian
2018-06-25 19:52 ` Marius Bakke
2018-06-25 21:07 ` Vagrant Cascadian
2018-06-25 21:20 ` Marius Bakke [this message]
2018-06-26 4:37 ` Vagrant Cascadian
2018-06-26 21:53 ` bug#31957: " Marius Bakke
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=87h8lqzhq0.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=31958@debbugs.gnu.org \
--cc=vagrant@debian.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.