Kei Kebreau writes:
> Alex Vong writes:
>
>> Mike Miller writes:
>>
>>> On Wed, Aug 10, 2016 at 14:43:57 +0800, Alex Vong wrote:
I thought it was an optional dependency because when I run
`./configure --help', it contains the following help:
--with-openssl use li
Alex Vong writes:
> Mike Miller writes:
>
>> On Wed, Aug 10, 2016 at 14:43:57 +0800, Alex Vong wrote:
>>> 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 ARG
Mike Miller writes:
> On Wed, Aug 10, 2016 at 14:43:57 +0800, Alex Vong wrote:
>> 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',
>>
Mike Miller writes:
> On Wed, Aug 10, 2016 at 00:28:04 -0400, Mark H Weaver wrote:
>> We should investigate the reason why it failed without OpenSSL. I would
>> start by repeating the build attempt without OpenSSL, and looking at the
>> resulting config.log to see what went wrong.
>
> Sounds goo
On Wed, Aug 10, 2016 at 14:43:57 +0800, Alex Vong wrote:
> 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' =
On Wed, Aug 10, 2016 at 00:28:04 -0400, Mark H Weaver wrote:
> We should investigate the reason why it failed without OpenSSL. I would
> start by repeating the build attempt without OpenSSL, and looking at the
> resulting config.log to see what went wrong.
Sounds good to me. Let us know what you
Mike Miller 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 oct
k...@openmailbox.org writes:
> On 2016-08-09 14:30, Ricardo Wurmus wrote:
>> Mike Miller 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?
>>>
>>
Mike Miller writes:
> I would recommend that you use a libcurl that is built against GnuTLS
> as we do on Debian.
Our libcurl is already built against GnuTLS.
Mark
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
> w
On 2016-08-09 14:30, Ricardo Wurmus wrote:
Mike Miller 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 an
Mike Miller 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 pa
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
On Sat, Aug 06, 2016 at 09:52:39AM +0800, Alex Vong wrote:
> Ricardo Wurmus writes:
>
> > Alex Vong writes:
> >
> >> I notice 'octave 4.0.2' has 'openssl@1.0.2h' as one of its inputs. As
> >> far as I know, gplv3 is incompatible with openssl license
> >> (https://people.gnome.org/~markmc/openssl
Ricardo Wurmus writes:
> Alex Vong writes:
>
>> I notice 'octave 4.0.2' has 'openssl@1.0.2h' as one of its inputs. As
>> far as I know, gplv3 is incompatible with openssl license
>> (https://people.gnome.org/~markmc/openssl-and-the-gpl.html).
>
> Looks like you’re right. Other projects add a sp
Alex Vong writes:
> John Darrington writes:
>
>> I would not be at all suprised if there were more incompatibilities like
>> this. Ought we not have a lint rule that checks this?
>>
> Indeed, in the short term, we could lint for special case, such that
> openssl appears as an input for an GPLv
John Darrington writes:
> I would not be at all suprised if there were more incompatibilities like
> this. Ought we not have a lint rule that checks this?
>
Indeed, in the short term, we could lint for special case, such that
openssl appears as an input for an GPLv[123](+) package.
In the lon
ng0 writes:
> John Darrington writes:
>
>> I would not be at all suprised if there were more incompatibilities like
>> this. Ought we not have a lint rule that checks this?
>>
>> J'
>>
>> On Fri, Aug 05, 2016 at 12:35:54AM +0800, Alex Vong wrote:
>> Hi guixes,
>>
>> First, cong
Alex Vong writes:
> I notice 'octave 4.0.2' has 'openssl@1.0.2h' as one of its inputs. As
> far as I know, gplv3 is incompatible with openssl license
> (https://people.gnome.org/~markmc/openssl-and-the-gpl.html).
Looks like you’re right. Other projects add a special openSSL linking
exception,
John Darrington writes:
> I would not be at all suprised if there were more incompatibilities like
> this. Ought we not have a lint rule that checks this?
>
> J'
>
> On Fri, Aug 05, 2016 at 12:35:54AM +0800, Alex Vong wrote:
> Hi guixes,
>
> First, congratulations to Ricardo Wur
I would not be at all suprised if there were more incompatibilities like
this. Ought we not have a lint rule that checks this?
J'
On Fri, Aug 05, 2016 at 12:35:54AM +0800, Alex Vong wrote:
Hi guixes,
First, congratulations to Ricardo Wurmus as new maintainer and the new
0.1
21 matches
Mail list logo
