unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Is anyone opposed to GnuTLS with DANE by default?
Date: Thu, 16 Nov 2017 15:25:38 +0000	[thread overview]
Message-ID: <20171116152538.vhdimw7yluaku7at@abyayala> (raw)
In-Reply-To: <87wp2qh6yj.fsf@gnu.org>

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

Ludovic Courtès transcribed 0.5K bytes:
> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> 
> > I certainly don't object, but am forced to note that ’gnutls-dane’ more
> > than doubles the closure size of ‘gnutls’ proper (294.2 MiB vs. 138.5).
> >
> > The only new input is ‘unbound’, but that manages to pull in both
> > Pythons 2 and 3. It would be nice™ if it could first be -minimalised...
> 
> Yes, to me that’s a showstopper.  (One of the Pythons comes from
> libevent.)
> 
> Thanks,
> Ludo’.

Okay, sounds reasonable to me and I agree, especially with Python not being
reproducible at the moment (if I remember the threads right).

Am I in the 'old system design' mindwset when I think that
every application that has applications such as libmicrohttpd
in its direct dependency chain should depend on the GnuTLS
version LMH uses and not the 'normal' GnuTLS
(It also depends on the features of GnuTLS which are being used,
but to be on the safe side)?
-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dl.n0.is/dist/keys/
  WWW: https://we.make.ritual.n0.is

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

  reply	other threads:[~2017-11-16 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 18:54 Is anyone opposed to GnuTLS with DANE by default? ng0
2017-11-14 19:22 ` Tobias Geerinckx-Rice
2017-11-14 20:13   ` Leo Famulari
2017-11-16 10:08   ` Ludovic Courtès
2017-11-16 15:25     ` ng0 [this message]
2017-11-16 16:16       ` Ludovic Courtès
2017-11-16 17:01         ` ng0
2017-11-17 20:53           ` 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

  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=20171116152538.vhdimw7yluaku7at@abyayala \
    --to=ng0@infotropique.org \
    --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 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).