From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Libressl
Date: Fri, 3 Jul 2015 22:26:11 +0200 [thread overview]
Message-ID: <20150703202611.GA26610@debian> (raw)
In-Reply-To: <87k2v4hdux.fsf@netris.org>
On Mon, Jun 15, 2015 at 05:16:06PM -0400, Mark H Weaver wrote:
> The license you pasted is the original SSLeay License, whereas
> <https://www.gnu.org/licenses/license-list.html#OpenSSL> says:
> The license of OpenSSL is a conjunction of two licenses, one of them
> being the license of SSLeay. You must follow both. [...]
>
> However, I see now that this is a bit confusing, and we made a mistake
> in our 'license' field of our OpenSSL package. My casual reading of the
> above text led me believe that the "OpenSSL License" is itself a
> conjunction of the two licenses, but I see that
> <http://directory.fsf.org/wiki/License:OpenSSL> does not include the
> SSLeay license.
>
> So, I think we should add 'ssleay' to (guix licenses) and then add it to
> the license field of 'openssl' along with a comment explaining that the
> requirements of both (all?) licenses must be followed.
So this looks essentially like a bug in
https://www.gnu.org/licenses/license-list.html#OpenSSL
Would you like to report it (where?)?
Then it would be good if the SSLeay license could be added as
org/wiki/License:...
before we add it to our license collection.
Andreas
next prev parent reply other threads:[~2015-07-03 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 19:11 [PATCH] Libressl Andreas Enge
2015-06-15 20:15 ` Mark H Weaver
2015-06-15 20:30 ` Andreas Enge
2015-06-15 21:16 ` Mark H Weaver
2015-07-03 20:26 ` Andreas Enge [this message]
2015-06-16 9:56 ` Ludovic Courtès
2015-07-03 19:57 ` Andreas Enge
2015-07-05 15:17 ` Andreas Enge
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=20150703202611.GA26610@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.