all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Is anyone opposed to GnuTLS with DANE by default?
Date: Fri, 17 Nov 2017 21:53:13 +0100	[thread overview]
Message-ID: <871skw4og6.fsf@gnu.org> (raw)
In-Reply-To: <20171116170134.zzcrwnzs6hafdr73@abyayala> (ng0@infotropique.org's message of "Thu, 16 Nov 2017 17:01:34 +0000")

ng0 <ng0@infotropique.org> skribis:

> Ludovic Courtès transcribed 0.5K bytes:
>> ng0 <ng0@infotropique.org> skribis:
>> 
>> > 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)?
>> 
>> You’re right, it’s a bad sign when there are two different variants of
>> the same package in a reference graph.
>> 
>> Ludo’.
>
> I haven't read much (or at all?) into guix lint so far,
> but can we lint for occurence of this pair somehow?

We could, but the problem is that we can’t determine if there’s an
actual problem until we’ve built it (we need to look at the reference
graph, not the package graph.)

Ludo’.

      reply	other threads:[~2017-11-17 20:53 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
2017-11-16 16:16       ` Ludovic Courtès
2017-11-16 17:01         ` ng0
2017-11-17 20:53           ` Ludovic Courtès [this message]

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=871skw4og6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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.