From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] OpenSSL 1.1.0
Date: Sat, 03 Sep 2016 16:34:51 +0200 [thread overview]
Message-ID: <87oa45jblg.fsf@gnu.org> (raw)
In-Reply-To: <20160903140613.GB12802@jasmine> (Leo Famulari's message of "Sat, 3 Sep 2016 10:06:13 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Sep 03, 2016 at 03:50:55PM +0200, Ludovic Courtès wrote:
>> Leo Famulari <leo@famulari.name> skribis:
>> > When I put "openssl" in the 'name' field, as attached, `guix build
>> > openssl` gives me 1.1.0, which is not right. The other *-next packages
>> > all seem to use "name-next" as the name.
>>
>> Yes, but it’s different. Guile 2.1, for instance, is the development
>> series, so it makes sense to give it a different name so users don’t end
>> up using the “wrong” series.
>>
>> Conversely, IIUC, OpenSSL 1.1.0 is the new stable series, no?
>
> 1.1.0 is the new stable series, but I haven't found any software that
> can use the new interface yet. So, I don't want to make 1.1.0 the
> default OpenSSL version in Guix. Does that make sense?
Yes, but as long the ‘openssl’ refers to 1.0.x, it doesn’t really matter
than the “openssl” package points to the latest one, no? Use can still
run “guix package -i openssl@1.0” if they want.
Ludo’.
next prev parent reply other threads:[~2016-09-03 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 1:59 [PATCH 0/1] OpenSSL 1.1.0 Leo Famulari
2016-09-02 1:59 ` [PATCH 1/1] gnu: openssl: Update to 1.1.0 Leo Famulari
2016-09-02 7:40 ` [PATCH 0/1] OpenSSL 1.1.0 Ricardo Wurmus
2016-09-02 12:43 ` Ludovic Courtès
2016-09-02 20:14 ` Leo Famulari
2016-09-02 20:30 ` Leo Famulari
2016-09-03 13:50 ` Ludovic Courtès
2016-09-03 14:06 ` Leo Famulari
2016-09-03 14:34 ` Ludovic Courtès [this message]
2016-09-04 2:20 ` Leo Famulari
2016-09-04 2:48 ` Leo Famulari
2016-09-05 20:35 ` Ludovic Courtès
2016-09-05 23:05 ` Leo Famulari
2016-09-06 12:29 ` Ludovic Courtès
2016-09-06 17:47 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa45jblg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).