[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OpenSSL updates
From: |
Leo Famulari |
Subject: |
Re: OpenSSL updates |
Date: |
Thu, 22 Sep 2016 13:47:26 -0400 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
On Thu, Sep 22, 2016 at 12:33:15PM -0400, Mark H Weaver wrote:
> Leo Famulari <address@hidden> writes:
> > +(define-public openssl-1.0.2i
>
> Should this be kept private? Otherwise, both patches look good to me,
> please push.
Good catch.
I also realized that these patches change what variable is used when
using 'openssl' with the Guix command-line tools.
Without these patches, `guix build openssl` uses
(@@ (gnu packages tls) openssl-next) [0]
With these patches, `guix build openssl` uses
(@@ (gnu packages tls) openssl-1.0.2i)
So, I put (replacement #f) in openssl-next, which restores the old
behavior. We don't want to replace openssl-next with openssl-1.0.2i.
Pushed HEAD to 163d93a6bd231596959e2e157b60eb964db85d04
[0] Is that the right way to describe a package variable? That's how I
use `guix build -e`.
signature.asc
Description: PGP signature