On 2016-08-09 14:30, Ricardo Wurmus wrote:
Mike Miller <mtmil...@octave.org> writes:
On Wed, Aug 10, 2016 at 00:00:59 +0800, Alex Vong wrote:
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.
The “openssl” package (along with “cyrus-sasl”) was added as a new
input
to our “octave” package in commit
b7b27a8f28746a488eeee489c71053059dc5a8dc, along with the upgrade from
4.0.0 to 4.0.2.
I don’t know why this was done. Maybe Kei could shed some light on
this.
~~ Ricardo
When I tried to build Octave 4.0.2, the build complained about missing
SSL
and SASL libraries. Adding gnutls as a dependency (Debian users are
advised
to use libcurl4-gnutls-dev) did not fix the issue, so I added OpenSSL to
stop the issue. It seems to me that Octave 4.0.2 (and 4.0.3, the most
recent
version) depends on SSL for curl usage, as curl allows Octave users to
issue
a "pkg install -forge [package_name]" command to install packages from
the
Octave Forge repo. I didn't know that the licenses were incompatible, so
now
we have to name (or correctly package) the Guix equivalent of
libcurl4-gnutls-dev.
