From: "Thompson, David" <dthompson2@worcester.edu>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Problem with pkgconfig source https redirect
Date: Wed, 10 Feb 2016 16:40:03 -0500 [thread overview]
Message-ID: <CAJ=RwfYzw9vo-xJ7v6zY+Ks03S5ZxNVR=G_rv=JQ94a8ERSoqQ@mail.gmail.com> (raw)
In-Reply-To: <20160210094344.7aff4457@debian-netbook>
On Wed, Feb 10, 2016 at 2:43 AM, Efraim Flashner <efraim@flashner.co.il> wrote:
> On Tue, 09 Feb 2016 20:56:59 -0600
> Christopher W Carpenter <mordocai@mordocai.net> wrote:
>
>> Talked about this on IRC davexunit, but there appears to be a circular dependency
>> issue with gnutls and pkg-config now that pkg-config needs to be
>> downloaded via https.
>>
> [snip]
>>
>> davexunit on #guix mentioned that this may need to be solved using a
>> minimal build of gnutls that doesn't require pkg-config for https
>> downloads but i'm a bit out of my depth here so I'm just reporting :).
>>
>> I am happy to do some grunt work once the project decides what direction
>> to go.
>>
>> Thanks,
>> Christopher Carpenter
>>
>
> Another option is to try to build gnutls without pkg-config and as part of
> the configure phase manually tell it where to find the dependencies. IIRC we
> do that with some of the less complicated lower level packages.
The bigger problem to be aware of is this: No package in the gnutls
dependency graph may have its source code downloaded over HTTPS. Even
if we hack around this for pkg-config, I'm sure it will bite us again
when another upstream starts enforcing HTTPS.
So, what can we do here?
- Dave
next prev parent reply other threads:[~2016-02-10 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 2:56 Problem with pkgconfig source https redirect Christopher W Carpenter
2016-02-10 7:43 ` Efraim Flashner
2016-02-10 21:40 ` Thompson, David [this message]
2016-02-11 9:48 ` 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='CAJ=RwfYzw9vo-xJ7v6zY+Ks03S5ZxNVR=G_rv=JQ94a8ERSoqQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=efraim@flashner.co.il \
--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).