> On May 21, 2017, at 22:16, Zero King wrote:
>
> On Sun, May 21, 2017 at 10:12:31PM -0500, Ryan Schmidt wrote:
>>
>>> On May 21, 2017, at 22:11, Zero King wrote:
>>>
>>> I'd prefer to keep the libressl port contents untouched. openssl and
>>> libressl install the same software too.
>>
>> Ob
On Sun, May 21, 2017 at 10:12:31PM -0500, Ryan Schmidt wrote:
On May 21, 2017, at 22:11, Zero King wrote:
I'd prefer to keep the libressl port contents untouched. openssl and
libressl install the same software too.
Obviously, they don't. openssl installs openssl. libressl installs libressl.
> On May 21, 2017, at 22:11, Zero King wrote:
>
> On Sun, May 21, 2017 at 09:59:28PM -0500, Ryan Schmidt wrote:
>>
>>> On May 21, 2017, at 21:50, Zero King wrote:
>>>
>>> Yes. For LibreSSL users libtls.dylib already exists so libtls won't be
>>> installed with this variant and for OpenSSL use
On Sun, May 21, 2017 at 09:59:28PM -0500, Ryan Schmidt wrote:
On May 21, 2017, at 21:50, Zero King wrote:
Yes. For LibreSSL users libtls.dylib already exists so libtls won't be
installed with this variant and for OpenSSL users libtls can be
installed. Most users already have one of them insta
> On May 21, 2017, at 21:50, Zero King wrote:
>
> On Sun, May 21, 2017 at 09:41:06PM -0500, Ryan Schmidt wrote:
>>
The libtls library, as shipped with LibreSSL 2.3.2 or later, is
required to use the HTTPS constraint feature, though it is not
required to use OpenNTPD.
>>>
>>> lib
On Sun, May 21, 2017 at 09:41:06PM -0500, Ryan Schmidt wrote:
The libtls library, as shipped with LibreSSL 2.3.2 or later, is
required to use the HTTPS constraint feature, though it is not
required to use OpenNTPD.
libtls.dylib will not be removed from libressl* ports. OpenNTPD requires
Libre
> On May 21, 2017, at 21:38, Zero King wrote:
>
> On Sun, May 21, 2017 at 09:24:50PM -0500, Ryan Schmidt wrote:
>>
>>> On May 21, 2017, at 21:23, Zero King wrote:
>>>
>>> On Sun, May 21, 2017 at 09:14:10PM -0500, Ryan Schmidt wrote:
Why does this https variant default to libressl (while
On Sun, May 21, 2017 at 09:24:50PM -0500, Ryan Schmidt wrote:
On May 21, 2017, at 21:23, Zero King wrote:
On Sun, May 21, 2017 at 09:14:10PM -0500, Ryan Schmidt wrote:
Why does this https variant default to libressl (while allowing openssl), when
other ports default to openssl (while allowi
> On May 21, 2017, at 21:23, Zero King wrote:
>
> On Sun, May 21, 2017 at 09:14:10PM -0500, Ryan Schmidt wrote:
>> Why does this https variant default to libressl (while allowing openssl),
>> when other ports default to openssl (while allowing libressl)? libressl is
>> *not* a drop-in replacem
On Sun, May 21, 2017 at 09:14:10PM -0500, Ryan Schmidt wrote:
Why does this https variant default to libressl (while allowing openssl), when
other ports default to openssl (while allowing libressl)? libressl is *not* a
drop-in replacement for openssl, in that ports have to be recompiled to use
> On May 18, 2017, at 13:32, Vincent wrote:
>
> Vincent (Veence) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/5dd0c4d6ce6d8adc6154143aa3153b39183ea45f
>
> commit 5dd0c4d6ce6d8adc6154143aa3153b39183ea45f
>
> Author: V
> On May 18, 2017, at 22:09, Zero King wrote:
>
> Zero King (l2dy) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/567f456fd11ec6bf1572cfa1c4c460e47f162c90
>
> The following commit(s) were added to refs/heads/master by t
> On May 20, 2017, at 12:44, Kurt Hindenburg wrote:
>
> Kurt Hindenburg (kurthindenburg) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/1dba19903c98ed9e104fe993dd7c70d4d810704d
>
> commit 1dba19903c98ed9e104fe993dd7c70d
13 matches
Mail list logo
