From: zimoun <zimon.toutoune@gmail.com>
To: John Soo <jsoo1@asu.edu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Parallel downloads
Date: Tue, 12 Nov 2019 17:48:16 +0100 [thread overview]
Message-ID: <CAJ3okZ02WivBN-PUPJhO5P1p3ZwAWXikgX9Xa7oBSc_EUr=DNw@mail.gmail.com> (raw)
In-Reply-To: <811C4D1E-A2D9-4661-9F10-C068FBE2CA80@asu.edu>
Hi,
It is not related with parallel download but on old machines "guix
build --no-substitutes" can eat a lot of resources; for example if the
package has a lot of dependencies. I would like to be able to list
which dependencies I want to build and which I want to substitute.
Maybe it is already possible.
Currently, I am doing:
guix build `guix show PKG | recsel -R dependencies`
guix build PKG --no-substitutes
What do you think?
All the best,
simon
next prev parent reply other threads:[~2019-11-12 16:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:07 Parallel downloads Pierre Neidhardt
2019-10-31 16:18 ` Tobias Geerinckx-Rice
2019-10-31 16:48 ` Pierre Neidhardt
2019-10-31 18:01 ` zimoun
2019-10-31 18:09 ` Pierre Neidhardt
2019-11-03 14:48 ` Ludovic Courtès
2019-11-03 15:29 ` Pierre Neidhardt
2019-11-06 15:34 ` Ludovic Courtès
2019-11-06 16:08 ` Pierre Neidhardt
2019-11-09 17:40 ` Ludovic Courtès
2019-11-10 13:28 ` Pierre Neidhardt
2019-11-12 15:36 ` Ludovic Courtès
2019-11-12 15:59 ` John Soo
2019-11-12 16:48 ` zimoun [this message]
2019-11-13 7:43 ` Efraim Flashner
2019-11-13 11:26 ` zimoun
2019-11-12 17:44 ` Leo Famulari
2019-11-17 17:15 ` Ludovic Courtès
2019-11-13 16:16 ` Mark H Weaver
2019-11-13 18:03 ` Pierre Neidhardt
2019-11-13 18:25 ` Leo Famulari
2019-11-13 19:34 ` Pierre Neidhardt
2019-12-13 9:35 ` Pierre Neidhardt
2019-12-13 12:25 ` Brett Gilio
2019-11-17 17:52 ` Ludovic Courtès
2019-11-06 21:26 ` Bengt Richter
2019-11-01 10:06 ` Joshua Branson
2019-11-01 19:11 ` Pierre Neidhardt
2019-11-03 14:50 ` 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='CAJ3okZ02WivBN-PUPJhO5P1p3ZwAWXikgX9Xa7oBSc_EUr=DNw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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).