all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/02: gnu: libressl: Update to 2.5.3.
Date: Thu, 13 Apr 2017 14:59:21 -0400	[thread overview]
Message-ID: <20170413185921.GD14931@jasmine> (raw)
In-Reply-To: <87mvbkny4y.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

On Thu, Apr 13, 2017 at 05:08:29PM +0200, Ludovic Courtès wrote:
> A simple approach is to force LibreSSL to always use its non-getentropy
> code, and lift this restriction once we clearly require newer kernels¹.
> The attached patch does that.
> 
> Thoughts?

> +     ;; Do as if 'getentropy' was missing since older Linux kernels lack it
> +     ;; and libc would return ENOSYS, which is not properly handled.
> +     '(#:configure-flags '("ac_cv_func_getentropy=no")))

If we are committed to building glibc with the 2.6 kernel headers, and
to providing substitutes for libressl and it's dependent packages, then
I think this patch is a good option.

But, it's a bit of a shame to leave this ~2.5 year old feature behind,
especially when the 2.6 Linux series is not even part of the Linux
long-term-support project. [0] These kernels *will* live for a long time
through support from RHEL; their most recent kernel on RHEL7 is 3.10.

However, I don't fully understand the impact of building glibc with a
newer set of headers, so my objection is a weak one :)

Personally, I don't think it's paramount to offer substitutes for the
packages in question. But I know this is an unpopular position, in
general :)

[0]
https://ltsi.linuxfoundation.org/
https://www.kernel.org/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-04-13 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170412011114.29557.46901@vcs0.savannah.gnu.org>
     [not found] ` <20170412011115.CE2FF220BE@vcs0.savannah.gnu.org>
2017-04-12  9:15   ` 01/02: gnu: libressl: Update to 2.5.3 Mark H Weaver
2017-04-12 15:20     ` Leo Famulari
2017-04-13 15:08       ` Ludovic Courtès
2017-04-13 18:59         ` Leo Famulari [this message]
2017-04-13 20:18           ` Leo Famulari
2017-04-14 12:43           ` Ludovic Courtès
2017-04-14 16:48             ` Leo Famulari
2017-04-14 18:07           ` Mark H Weaver
2017-04-19 20:12             ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170413185921.GD14931@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.