From: Ricardo Wurmus <rekado@elephly.net>
To: ng0@n0.is
Cc: guix-devel@gnu.org
Subject: Re: [bug#30165] [PATCH] gnu: gnurl: Add '--with-ca-bundle' path to configure-flags.
Date: Wed, 24 Jan 2018 15:40:54 +0100 [thread overview]
Message-ID: <87y3knxqtl.fsf@elephly.net> (raw)
In-Reply-To: <87d11zv19n.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>
ng0@n0.is writes:
> Why? Why are we waiting for months and months and months to
> patch every single application instead of simply fixing cURL
> or our build of cURL and close this case?
This is only about libcurl. Libcurl expects that a user (i.e. a
programme linking with libcurl) sets the certificate bundle. This
happens in different ways in different applications. Libcurl
purposefully ignores the usual environment variables, because those are
meant for the “curl” command line tool only.
There also is no bug report in the bug tracker. Instead of demanding an
answer to why this hasn’t “simply” been fixed, I encourage you to
(re-)read the previous discussions about this:
https://lists.gnu.org/archive/html/guix-devel/2017-01/msg00516.html
https://lists.gnu.org/archive/html/guix-devel/2014-02/msg00245.html
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-01-24 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 1:55 [bug#30165] [PATCH] gnu: gnurl: Add '--with-ca-bundle' path to configure-flags Adam Van Ymeren
2018-01-24 11:52 ` ng0+guixpatches
2018-01-24 13:23 ` ng0
2018-01-24 14:40 ` Ricardo Wurmus [this message]
2018-01-24 17:00 ` Adam Van Ymeren
2018-01-24 17:00 ` Adam Van Ymeren
2018-01-24 17:56 ` ng0
2018-01-24 18:15 ` Adam Van Ymeren
-- strict thread matches above, loose matches on Subject: below --
2018-01-18 23:07 ng0+guixpatches
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=87y3knxqtl.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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.