<Apteryx>rekado: Maybe there should be the ampersand (&) at the end of the command in 8.2 of the manual, because it does look like we should type sequentially the two commands to achieve a build, and there's no mention that the first one never returns.
<Apteryx>Am I supposed to run the "pre-inst-env" prefixed commands inside a guix environment? Or is this taken care of by the script.
<bavier>Apteryx: it doesn't need to be inside a guix environment
<Apteryx>After the bootstrap, configure and make check, yes, that's what I was attempting now (start daemon using pre-inst-env, then try building my package using ./pre-inst-env guix build udisks.
<Apteryx>I noticed that when I start the daemon it replaces any guix-daemon currently running.
<Apteryx>I'll go through these steps again and let you know of the result! Thanks.
<bavier>if you have a daemon already running, you don't need to start another
<Apteryx>bavier: I wanted to use everything guix related from its git, just for the sake of it.
<Apteryx>But yes, if I can't get it working I'll fallback to using my working daemon (default build).
<Apteryx>Is this something dangerous to have such a collision when I run "guix environment guix": warning: collision encountered: /gnu/store/5k8z2aj8ca16nmvwvdsl0mdc3slm14k2-ld-wrapper-0/bin/ld /gnu/store/z53lxlrp7061vggbnhpxcsmad6lx96p8-binutils-2.25.1/bin/ld ?
<Apteryx>Seems like potentially a normal side-effect of the "environment" command, given the "wrapper" in the path.