From: ludo@gnu.org (Ludovic Courtès)
To: rekado <rekado@elephly.net>
Cc: 19315-done@debbugs.gnu.org
Subject: bug#19315: per-user profile directory not created/mentioned
Date: Sun, 04 Jan 2015 23:43:46 +0100 [thread overview]
Message-ID: <87fvbq180t.fsf@gnu.org> (raw)
In-Reply-To: <874mt5159y.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 09 Dec 2014 11:33:45 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> rekado <rekado@elephly.net> skribis:
>
>> the manual does not mention that a per-user profile directory owned by
>> the user account has to be created after installation of guix.
>
> It actually does, under “Invoking guix package” (see
> <http://www.gnu.org/software/guix/manual/html_node/Invoking-guix-package.html#Invoking-guix-package>):
>
> In a multi-user setup, user profiles must be stored in a place
> registered as a "garbage-collector root", which ‘$HOME/.guix-profile’
> points to (*note Invoking guix gc::). That directory is normally
> ‘LOCALSTATEDIR/profiles/per-user/USER’, where LOCALSTATEDIR is the value
> passed to ‘configure’ as ‘--localstatedir’, and USER is the user name.
> It must be created by ‘root’, with USER as the owner. When it does not
> exist, or is not owned by USER, ‘guix package’ emits an error about it.
>
> Would you suggest making it more prominent somehow?
Commit 15ddeff merges code from nix-daemon. Among other things, it adds
code to create this ‘profiles/per-user’ directory with appropriate
permissions (see LocalStore::LocalStore(bool reserveSpace) in
local-store.cc.)
Commit 4379c35 updates the manual accordingly.
Thanks,
Ludo’.
prev parent reply other threads:[~2015-01-04 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 21:31 bug#19315: per-user profile directory not created/mentioned rekado
2014-12-09 10:33 ` Ludovic Courtès
2015-01-04 22:43 ` Ludovic Courtès [this message]
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=87fvbq180t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19315-done@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.