From: Efraim Flashner <efraim@flashner.co.il>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Building many packages in order
Date: Fri, 21 Oct 2016 14:53:02 +0300 [thread overview]
Message-ID: <20161021115302.GA26768@macbook42.flashner.co.il> (raw)
In-Reply-To: <5809F448.5030508@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Fri, Oct 21, 2016 at 12:56:08PM +0200, Hartmut Goebel wrote:
> Hi,
>
> testing the new python build system I’m seeking for some way to build
> *many* packages in order.
>
> Of course I can just run `guix build` with the list of packages to be
> build. But when building all python packages, the list gets rather long
> and does not fit into one call of `guix build` (due to the number of
> arguments xargs passes to the command is restricted). Thus only
> partitions of the packages are build in order.
>
> So I need some way for passing *all* packages to be build to `guix build`.
>
> Any hints?
>
If you want to build all packages that are python- or python2-, then you
can call 'guix build $(guix package -A ^python | cut -f1)'
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)'
Both of these as written will stop when they encounter a package that
doesn't build. I'm sure there's also a scheme-y way of doing it.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-10-21 11:53 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 [this message]
2016-10-21 12:23 ` Hartmut Goebel
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
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=20161021115302.GA26768@macbook42.flashner.co.il \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).