From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Building many packages in order
Date: Fri, 21 Oct 2016 14:23:17 +0200 [thread overview]
Message-ID: <580A08B5.3020504@crazy-compilers.com> (raw)
In-Reply-To: <20161021115302.GA26768@macbook42.flashner.co.il>
Am 21.10.2016 um 13:53 schrieb Efraim Flashner:
> If you want to build all packages that are python- or python2-, then you
> can call 'guix build $(guix package -A ^python | cut -f1)'
I was about to answer that this will not work if the length of the
arguments string exceeds some limit. This made me re-check my premises
and found they are wrong: Both the length of the commands line and the
number of arguments to be passed to a new process are *really* big. See [1].
So I checked again and my command line is about 18,000 characters long
and even xargs calls `guix build` only once.
So my premises was irrelevant and my "mass rebuild" script works as
expected.
> If you want all the packages that rely on python or python-2, then you
> can call 'guix build $(guix refresh -l python python@2 | cut -d':' -f2)'
Thanks for this trick. I'm not used to "guix refresh" and my code for
selecting the packages is much more complicated. (I select them by
name.) I really have to get more common with these guix subcommands.
[1]
http://unix.stackexchange.com/questions/120642/what-defines-the-maximum-size-for-a-command-single-argument
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2016-10-21 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 10:56 Building many packages in order Hartmut Goebel
2016-10-21 11:18 ` Roel Janssen
2016-10-21 12:15 ` Hartmut Goebel
2016-10-21 11:53 ` Efraim Flashner
2016-10-21 12:23 ` Hartmut Goebel [this message]
2016-10-21 19:44 ` Leo Famulari
2016-10-22 15:47 ` Efraim Flashner
2016-10-23 17:10 ` Hartmut Goebel
2016-10-24 13:56 ` Ricardo Wurmus
2016-11-06 16:04 ` Hartmut Goebel
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=580A08B5.3020504@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--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 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.