From: Christopher Baines <mail@cbaines.net>
To: ng0 <ng0@infotropique.org>
Cc: 28170@debbugs.gnu.org
Subject: [bug#28170] Add gnutls/dane + use it where its needed (gnurl, libmicrohttpd, gnunet)
Date: Sat, 30 Sep 2017 13:43:46 +0100 [thread overview]
Message-ID: <20170930134346.54a4c54a@cbaines.net> (raw)
In-Reply-To: <20170930122309.akl2dxa46eru36pb@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
On Sat, 30 Sep 2017 12:23:09 +0000
ng0 <ng0@infotropique.org> wrote:
> Christopher Baines transcribed 2.1K bytes:
> > On Mon, 21 Aug 2017 09:57:26 +0000
> > ng0 <ng0@infotropique.org> wrote:
> >
> > > The dependency chain of GNUnet demands GnuTLS with DANE support.
> > > You can use it without DANE, but there are certain parts which
> > > will not work. DANE is recommended. (ports of FREEBSD uses
> > > gnutls-dane for libmicrohttpd aswell for example).
> >
> > > From c9dedfd1a6f91d557006b00505a428be84102b1e Mon Sep 17 00:00:00
> > > 2001 From: ng0 <ng0@infotropique.org>
> > > Date: Mon, 21 Aug 2017 09:28:51 +0000
> > > Subject: [PATCH 1/4] gnu: gnutls: Add 'gnutls-dane'.
> > >
> > > * gnu/packages/tls.scm (gnutls/dane): New variable.
> >
> > Hey, so I'm trying to do some reviewing.
> >
> > What was your reasoning for creating a new gnutls/dane package,
> > rather than adding unbound to the existing gnutls package?
> >
> > I don't know much about GnuTLS, but it would be good to make it
> > clear why this approach was taken, especially in the commit message
> > and by the gnutls/dane package definition.
>
> Honestly, I did not want to touch the gnutls package for this.
> I wanted to leave the option open to have gnutls without dane.
> Sure, it's a useful feature. If you think I should apply it
> directly to gnutls, tell me and I'll send a new patch.
I'm happy with that reason, if you could put that in the relevant
commit message, or in a comment by the gnutls/dane package definition
(or both), I'll check I can build all the changed packages, and push
if they all build for me.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-09-30 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 9:57 [bug#28170] Add gnutls/dane + use it where its needed (gnurl, libmicrohttpd, gnunet) ng0
2017-09-30 11:26 ` Christopher Baines
2017-09-30 12:23 ` ng0
2017-09-30 12:43 ` Christopher Baines [this message]
2017-09-30 14:01 ` ng0
2017-09-30 14:12 ` ng0
2017-09-30 14:34 ` Christopher Baines
2017-09-30 14:56 ` ng0
2017-09-30 15:01 ` ng0
2017-09-30 16:05 ` Christopher Baines
2017-09-30 16:36 ` ng0
2017-09-30 17:38 ` Christopher Baines
2017-10-01 9:52 ` bug#28170: " Christopher Baines
2017-09-30 14:03 ` [bug#28170] " ng0
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=20170930134346.54a4c54a@cbaines.net \
--to=mail@cbaines.net \
--cc=28170@debbugs.gnu.org \
--cc=ng0@infotropique.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).