unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: openssl is now a dependency of guix: possible license conflict?
Date: Wed, 16 Aug 2017 22:29:57 -0400	[thread overview]
Message-ID: <87y3qjncyi.fsf@netris.org> (raw)
In-Reply-To: <87tw17ox0x.fsf@gmail.com> (Alex Vong's message of "Thu, 17 Aug 2017 08:31:10 +0800")

Hi Alex,

Alex Vong <alexvong1995@gmail.com> writes:

> Recently, guix changes to use guile-git for 'guix pull', which is a
> libgit2 binding for guile, while libgit2 itself uses openssl to talk
> over https.
>
> Now the potential problem is that guix is licensed in gpl3+ while
> openssl is licensed in openssl. It is well-known the two licenses have
> incompatibility disallowing one from distributing the result of linking
> a gpl program with openssl[0].

Thanks for bringing this to our attention.  I looked into this, and it
turns out that Debian's libgit2 package no longer depends on OpenSSL:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798421

libgit2 can use libcurl for HTTPS support, in which case it does not
need OpenSSL.  Our libcurl already uses GnuTLS instead of OpenSSL.  So,
I expect this issue can be easily resolved.  I'll work on it.

     Thanks,
       Mark

  reply	other threads:[~2017-08-17  2:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  0:31 openssl is now a dependency of guix: possible license conflict? Alex Vong
2017-08-17  2:29 ` Mark H Weaver [this message]
2017-08-17  7:36   ` Mark H Weaver
2017-08-18 14:44     ` Alex Vong
2017-08-18 18:06       ` Leo Famulari
2017-08-18 21:21     ` Mark H Weaver
2017-08-19 12:51       ` Adonay Felipe Nogueira
2017-08-22  8:32       ` Ludovic Courtès

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=87y3qjncyi.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel@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. 
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).