From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Qt 5.11 tarballs anyone?
Date: Mon, 25 Jan 2021 20:43:47 +0100 [thread overview]
Message-ID: <86mtwwkdjg.fsf@gmail.com> (raw)
In-Reply-To: <87eei9558q.fsf@inria.fr>
Hi Ludo,
On Mon, 25 Jan 2021 at 17:52, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
>> How could I list all the tarballs that ci.guix.gnu.org has?
>
> I suppose you could simply run something like:
>
> guix build -n --sources=all $(guix package -A | cut -f1)
This will download only the source at the current Guix.
Well, I would like to 1. stress disarchive to evaluate how its database
disarchive-db scales, and 2. have a number about the size of all
tarballs that Guix is able to reach (say post 1.0).
> and see what happens.
>
> That said, I think Chris Baines recently added something to the Guix
> Data Service that periodically tries to build fixed-output derivations
> (essentially source code downloads). Am I right, Chris?
Cool!
Maybe a Berlin or Bayfront sysadmin could list all the tarballs files in
the store and publish this file. Then I could use “guix download” to
fetch all of them.
All the best,
simon
next prev parent reply other threads:[~2021-01-25 19:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 11:46 Qt 5.11 tarballs anyone? Ludovic Courtès
2021-01-24 12:08 ` Tobias Geerinckx-Rice
2021-01-24 22:21 ` Ludovic Courtès
2021-01-24 14:21 ` Ludovic Courtès
2021-01-25 11:18 ` zimoun
2021-01-25 16:52 ` Ludovic Courtès
2021-01-25 18:49 ` Christopher Baines
2021-01-25 19:46 ` zimoun
2021-01-25 20:12 ` Christopher Baines
2021-01-25 20:17 ` zimoun
2021-01-26 8:39 ` Ludovic Courtès
2021-01-25 19:43 ` zimoun [this message]
2021-01-26 8:54 ` zimoun
2021-01-28 7:47 ` Ludovic Courtès
2021-02-01 14:31 ` Failure guix build --sources=all $(guix package -A zimoun
2021-02-02 13:00 ` Ludovic Courtès
2021-02-02 14:39 ` Maxim Cournoyer
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=86mtwwkdjg.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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).