all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: What's the state of (guix build download-nar)?
Date: Wed, 08 Feb 2023 10:08:15 +0100	[thread overview]
Message-ID: <87o7q4zfr4.fsf@gnu.org> (raw)
In-Reply-To: <871qn2erqp.fsf@cbaines.net> (Christopher Baines's message of "Mon, 06 Feb 2023 16:25:33 +0100")

Hi Chris!

Christopher Baines <mail@cbaines.net> skribis:

> I guess this raises two things in my mind. I'm not sure this'll work
> well given the not so recent changes to ci.guix.gnu.org. This module
> looks to rely on gzipped or uncompressed nars. I'm not sure uncompressed
> nars are available, and gzipped ones are no longer available.
>
> The second question is around the relation to bordeaux.guix.gnu.org, is
> it worth trying to support fetching nars from bordeaux.guix.gnu.org
> here, and what would be the best way of doing that? It wouldn't be too
> hard to add support for decomressed nars I think if that's a good
> approach?

Uh, that module needs love indeed.

Currently it’s used by some of the (guix VCS-download) modules.  I think
we should just update to (1) use lzip instead of gzip, and (2) have it
check ci.guix.gnu.org + bordeaux.guix.gnu.org.

Would you like to give it a try?

Thanks,
Ludo’.


  reply	other threads:[~2023-02-08  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 15:25 What's the state of (guix build download-nar)? Christopher Baines
2023-02-08  9:08 ` Ludovic Courtès [this message]
2023-02-08  9:24   ` Christopher Baines
2023-03-11 20:42     ` Christopher Baines
2023-02-09 14:16   ` Maxim Cournoyer
2023-02-09 15:41     ` Christopher Baines
2023-04-11 13:34     ` Simon Tournier

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=87o7q4zfr4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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.