Hi, Thomas!
Thomas Schwinge <tho...@codesourcery.com> skribis:
> I'm not a fan of extracting tarballs inside populated directories; so I'm
> in favor on the suggested change to extract inside a temporary directory,
> and then move everything in place as a separate step.
OK. I had come to the conclusion that yes, doing it in two steps is
reasonable, but it’s the user’s choice, and I wondered whether
describing the additional steps in the manual would make things look
more complicated than they are. WDYT?
> $ sudo ls -ld /root/.guix-profile /var/guix /gnu
> drwxr-xr-x 3 30001 30000 4096 Mai 14 10:36 /gnu
> lrwxrwxrwx 1 30001 30000 45 Mai 14 10:36 /root/.guix-profile ->
> /var/guix/profiles/per-user/root/guix-profile
> drwxr-xr-x 6 30001 30000 4096 Mai 14 10:36 /var/guix
>
> Should the tarball be packed such that it uses UID:GID 0:0, which -- I
> think? -- is always expected to map to root:root?
Yes, it was fixed in 01dbc7e.
> Which UID:GID should I now chown the files to?
root:root.
> It's very common, but I don't think there's a hard requirement for the
> root user's home directory to be /root. Maybe instead of shipping it in
> the tarball, the symbolic link should be created by an explicit command?
>
> $ sudo ln -sf /var/guix/profiles/per-user/root/guix-profile
> ~root/.guix-profile
Yes, why not. What do people think?
> <http://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html>.
>
> $ sudo groupadd --system guix-builder
> $ for i in `seq 1 10`; do sudo useradd -g guix-builder -G guix-builder -d
> /var/empty -s `which nologin` -c "Guix build user $i" --system
> guix-builder$i; done
>
> Please describe why ten is a good amount of Guix build users.
I’ve added this:
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -478,6 +478,9 @@ Bash syntax and the @code{shadow} commands):
@end example
@noindent
+The number of build users determines how many build jobs may run in
+parallel, as specified by the @option{--max-jobs} option
+(@pxref{Invoking guix-daemon, @option{--max-jobs}}).
The @code{guix-daemon} program may then be run as @code{root} with:
Thanks for providing feedback!
Ludo’.
