all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Mike Miller <mtmiller@octave.org>
Cc: guix-devel@gnu.org, help-octave@gnu.org
Subject: Re: octave license is incompatible with openssl
Date: Wed, 10 Aug 2016 14:43:57 +0800	[thread overview]
Message-ID: <87k2fpktsi.fsf@gmail.com> (raw)
In-Reply-To: <20160809172728.b6wijrzccd5wdv37@galago.mtmxr.com> (Mike Miller's message of "Tue, 9 Aug 2016 10:27:28 -0700")

Mike Miller <mtmiller@octave.org> writes:

> On Wed, Aug 10, 2016 at 00:00:59 +0800, Alex Vong wrote:
>> Hi octave devs,
>> 
>> During a look of the octave package in guix (a functional package
>> manager, part of gnu), we notice octave have an optional dependency on
>> openssl.
>> 
>> However, since the license of octave (gpl3+) is incompatible
>> with that of openssl
>> (https://people.gnome.org/~markmc/openssl-and-the-gpl.html), the
>> resulting binary after linking is not re-distributable.
>
> Agreed.
>
>> So, we drop the optional dependency to avoid the problem.
>
> Precisely what is the optional dependency that is dropped?
>
> Octave does not directly link with OpenSSL nor use any OpenSSL
> functions. The Octave package on Debian builds with all optional
> dependencies enabled, and the resulting binary is linked with GnuTLS.
>
I thought it was an optional dependency because when I run
`./configure --help', it contains the following help:

  --with-openssl          use libcrypto hash routines. Valid ARGs are: 'yes',
                          'no', 'auto' => use if available, 'optional' => use
                          if available and warn if not available; default is
                          'no'


Perhaps someone unaware of the issue adds this? Should I open a bug
report on this?

>> Is there any plan to fix this problem? There are some solutions we think
>> of: 1. add openssl linking exception to the license 2. provide support
>> for linking with gnutls as an alternative. In any case, I think we
>> should warn the user about it.
>> 
>> What are your ideas? (the messages below include the whole discussion on
>> the guix-devel mailing list)
>
> The Octave Guix package may be indirectly linking with OpenSSL through a
> direct dependency such as libcurl. I would recommend that you use a
> libcurl that is built against GnuTLS as we do on Debian.
>
Indeed, the Debian package does not depend on openssl.

> AFAICS, nothing needs to be fixed in Octave.
>
> HTH,

Thanks,
Alex

  parent reply	other threads:[~2016-08-10  6:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 16:35 octave license is incompatible with openssl Alex Vong
2016-08-04 17:10 ` John Darrington
2016-08-04 17:20   ` ng0
2016-08-05  9:08     ` Alex Vong
2016-08-05  9:03   ` Alex Vong
2016-08-05 11:43     ` Mathieu Lirzin
2016-08-05  6:50 ` Ricardo Wurmus
2016-08-06  1:52   ` Alex Vong
2016-08-08 20:00     ` Leo Famulari
2016-08-09 16:00       ` Alex Vong
2016-08-09 17:27         ` Mike Miller
2016-08-09 18:30           ` Ricardo Wurmus
2016-08-09 21:33             ` kei
2016-08-10  4:28               ` Mark H Weaver
2016-08-11  5:56                 ` Mike Miller
2016-08-11  9:58                   ` Mark H Weaver
2016-08-10  4:23           ` Mark H Weaver
2016-08-10  6:43           ` Alex Vong [this message]
2016-08-11  6:26             ` Mike Miller
2016-08-11 15:27               ` Alex Vong
2016-08-11 17:04                 ` Kei Kebreau
2016-08-13 12:37                   ` Alex Vong
2016-08-12 11:45                 ` JIT compiling Jordi Gutiérrez Hermoso
2016-08-12 15:08                   ` Sergei Steshenko
2016-08-12 16:06                     ` Oliver Heimlich
2016-08-13  1:03                       ` Sergei Steshenko
2016-08-13 11:48                         ` Alex Vong
2016-08-13 12:12                   ` Alex Vong
2016-08-14  8:07                     ` Sergei Steshenko
2016-08-14 10:21                       ` Francesco Potortì
2016-08-14 20:20                       ` Jordi Gutiérrez Hermoso

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=87k2fpktsi.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=help-octave@gnu.org \
    --cc=mtmiller@octave.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.