unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnurl: add CA path to configure-flags
Date: Sun, 12 Jun 2016 15:56:22 +0000	[thread overview]
Message-ID: <20160612155622.GB26362@khazad-dum> (raw)
In-Reply-To: <20160612142215.GA20253@solar>

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

On 2016-06-12(04:22:15+0200), Andreas Enge wrote:
> Hello,
>
> On Sat, Jun 11, 2016 at 08:51:28PM +0000, ng0 wrote:
> > * gnurl(configure-flags): --with-ca-path=/etc/ssl/certs/
>
> my impression is that this absolute path does not do what we would like
> it to. Optimally, the user would decide, by installing a certificate bundle
> into the profile, which certificates to use. And on a foreign distro, the
> random certificate bundle in /etc/ssl/certs, which does not come from Guix,
> would be used by the Guix gnurl, which would be surprising.
>
> Andreas

It is not entirely clear to me anymore why this was suggested to me
in the past 4 months.
I am aware of the differences, so maybe this could point to where
ever the /ssl/certs/ are?

When you know that gnurl does not need this, we're all good without
this change.
Gnurl so far is just curl with some project recommended build switches,
so if guix' curl detects the ssl/certs/ dir, gnurl should too.

--
♥Ⓐ ng0
For non-prism friendly talk find me on
psyced.org / loupsycedyglgamf.onion

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2016-06-12 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 20:51 [PATCH] gnurl: add CA path to configure-flags ng0
2016-06-12 14:22 ` Andreas Enge
2016-06-12 15:56   ` ng0 [this message]
2016-06-13 14:43   ` Ludovic Courtès
2016-06-13 15:38     ` ng0
2016-06-14 10: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

  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=20160612155622.GB26362@khazad-dum \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@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).