unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: LibreSSL?
Date: Mon, 20 Jun 2022 00:17:38 +0200	[thread overview]
Message-ID: <Yq+ggiZfpw/JBKPu@jurong> (raw)
In-Reply-To: <87lewpp55k.fsf@gnu.org>

Hello,

Am Fri, Apr 01, 2022 at 10:41:11AM +0200 schrieb Ludovic Courtès:
> At first sight, it looks like an easy-to-maintain package: no
> dependencies, few users, stable API.
> 
> I tried to update it to 3.5.1 and was proved wrong though: there’s one
> test failure in ‘tests/asn1object’ and the Internet doesn’t seem to know
> how to address the problem.  So it would need a bit more work.
> 
> I’d lean towards keeping it and doing that extra work, collectively, but
> I understand this very discussion shows that it’s debatable.

at some point in time, my understanding was that we would switch everything
to libressl and drop openssl. I have not followed, but from
   https://lwn.net/Articles/841664/
it looks as if the problems with openssl are more or less solved, at least
they are not worse than in libressl.

So an option would be to try to switch the existing dependencies to openssl
and decide from there.

What do you think?

Andreas



  reply	other threads:[~2022-06-19 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 16:39 LibreSSL? Leo Famulari
2022-04-01  8:41 ` LibreSSL? Ludovic Courtès
2022-06-19 22:17   ` Andreas Enge [this message]
2022-06-20 10:44     ` LibreSSL? Efraim Flashner

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=Yq+ggiZfpw/JBKPu@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=ludo@gnu.org \
    /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).