unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix binary tarball
Date: Sun, 07 Jun 2015 18:14:56 +0200	[thread overview]
Message-ID: <87zj4bxzpb.fsf@gnu.org> (raw)
In-Reply-To: <87d217itfr.fsf@kepler.schwinge.homeip.net> (Thomas Schwinge's message of "Sun, 7 Jun 2015 14:39:20 +0200")

[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]

Hi, Thomas!

Thomas Schwinge <thomas@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:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 382 bytes --]

--- 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:

[-- Attachment #3: Type: text/plain, Size: 46 bytes --]


Thanks for providing feedback!

Ludo’.

  parent reply	other threads:[~2015-06-07 16:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 16:46 Guix binary tarball Andreas Enge
2015-05-15 17:14 ` Ludovic Courtès
2015-05-15 17:37   ` Andreas Enge
2015-05-15 19:45     ` Taylan Ulrich Bayırlı/Kammer
2015-05-16 18:55       ` Ludovic Courtès
2015-05-16  2:53     ` Mark H Weaver
2015-05-17 21:34       ` Ludovic Courtès
2015-05-16  6:47   ` Andreas Enge
2015-05-16 18:57     ` Ludovic Courtès
2015-05-17 22:15   ` Ludovic Courtès
2015-05-17 22:45     ` Ludovic Courtès
2015-05-18 11:34       ` Andreas Enge
2015-05-18 19:38         ` Ludovic Courtès
2015-05-19 23:03 ` Mark H Weaver
2015-05-20  8:10   ` Andreas Enge
2015-05-20 10:19   ` Ludovic Courtès
2015-05-20 19:12     ` Mark H Weaver
2015-05-21  8:16       ` Ludovic Courtès
2015-06-07 12:39 ` Thomas Schwinge
2015-06-07 13:16   ` /run/current-system (was: Guix binary tarball) Thomas Schwinge
2015-06-07 16:19     ` /run/current-system Ludovic Courtès
2015-06-07 16:14   ` Ludovic Courtès [this message]
2015-06-08  9:34     ` Guix binary tarball Alex Kost
2015-06-08 21:33       ` Ludovic Courtès

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=87zj4bxzpb.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=thomas@codesourcery.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).