From: "Ludovic Courtès" <ludo@gnu.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 36630@debbugs.gnu.org
Subject: [bug#36630] [PATCH] guix: parallelize building the manual-database
Date: Thu, 18 Jul 2019 15:46:18 +0200 [thread overview]
Message-ID: <87zhlbe9qt.fsf@gnu.org> (raw)
In-Reply-To: <87k1cfpq0k.fsf@web.de> (Arne Babenhauserheide's message of "Thu, 18 Jul 2019 12:59:23 +0200")
Arne Babenhauserheide <arne_bab@web.de> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Did you try the ‘guix environment -n’ command above? Doesn’t it show
>> the manual-database.drv?
>
> It does show the manual database, but then running guix build
> /gnu/....drv --check does not run my changed code.
>
> I’m doing
>
> time ./pre-inst-env guix build /gnu/store/jnkxwwxk71n07fs6naa11fxmg3vpnnb3-manual-database.drv --check
>
> But it runs the installed guix, not the local changes to profile.scm.
Right, sorry for being unclear: you need to run
./pre-inst-env guix environment -n …
That will run you modified code and thus create a manual-database.drv
that uses your code; it’s this manual-database.drv that you should pass
to ‘guix build’.
HTH,
Ludo’.
next prev parent reply other threads:[~2019-07-18 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 21:42 [bug#36630] [PATCH] guix: parallelize building the manual-database Arne Babenhauserheide
2019-07-15 16:12 ` Ludovic Courtès
2019-07-15 23:32 ` Arne Babenhauserheide
2019-07-16 21:14 ` Ludovic Courtès
2019-07-17 22:06 ` Arne Babenhauserheide
2019-07-18 8:55 ` Ludovic Courtès
2019-07-18 8:57 ` Ludovic Courtès
2019-07-18 10:59 ` Arne Babenhauserheide
2019-07-18 13:46 ` Ludovic Courtès [this message]
2019-07-18 20:03 ` Arne Babenhauserheide
2019-10-23 20:01 ` Arne Babenhauserheide
2020-03-31 13:02 ` bug#36630: " Ludovic Courtès
2019-10-23 19:59 ` [bug#36630] [PATCH] use two threads to build man-pages and secure output msgs with mutex Arne Babenhauserheide
2019-10-27 16:27 ` Arne Babenhauserheide
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=87zhlbe9qt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36630@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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.