From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: non-root store
Date: Tue, 08 Dec 2020 12:19:55 +0100 [thread overview]
Message-ID: <87zh2ov92c.fsf@gnu.org> (raw)
In-Reply-To: <87wnxv56f7.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 06 Dec 2020 15:57:00 +0100")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> recently I’ve been playing with “guix pack -RR” and I’m very happy to
> see how well it works. Now I wonder if we could use the very same
> mechanism to wrap guix-daemon and let it manage a store directory that
> is not located at /gnu/store.
Yesss!
> Surely somebody has already tried this?
I did some time ago:
https://lists.gnu.org/archive/html/guix-devel/2018-05/msg00139.html
The environment variable names changed in the meantime, I guess you’d
need to set GUIX_STATE_DIRECTORY now.
> A common complaint about Guix is that it requires root permissions to
> install, which is “scary” and may seem unnecessary on single-user
> systems. By wrapping guix-daemon so that it uses file system
> virtualization (via user namespaces, proot, or the glibc debug hack) we
> could eliminate this obstacle.
>
> What do you think? Am I missing something obvious?
I think it’d be great to streamline this use case. We could even ship a
-RR tarball in the future, though we need to think about all the
implications.
One of them is that we’d probably need to include a shell in the bundle,
so that users can “enter” the file system view that includes /gnu/store.
Alternatively, we could provide a package transformation option that
“relocatable-wraps” executables, using ‘wrapped-package’ from (guix
scripts pack).
Thoughts?
Ludo’.
prev parent reply other threads:[~2020-12-08 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 14:57 non-root store Ricardo Wurmus
2020-12-06 16:07 ` Pjotr Prins
2020-12-08 11:19 ` 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
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=87zh2ov92c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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 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).