From: "Ludovic Courtès" <ludo@gnu.org>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Propose to distribute a user-only install script, not admin required
Date: Sun, 24 May 2020 22:42:51 +0200 [thread overview]
Message-ID: <877dx112us.fsf@gnu.org> (raw)
In-Reply-To: <CAFkJGRcqFGi9sQL7GLwBEVr_0YQ9THGfX9-VxgpTxgcvTaJr1Q@mail.gmail.com> (Josh Marshall's message of "Sat, 16 May 2020 11:25:08 -0400")
Hi Josh,
Josh Marshall <joshua.r.marshall.1991@gmail.com> skribis:
> One thing which I think could significantly aid adoption would be up
> either add an option or add a new installer script with guix
> configured to install and run purely out of the user's home directory
> without any special permissions. Conceptually, guix shouldn't need to
> have any elevated permissions given it is acceptable to use resources
> less efficiently when they are in contention. This would also allow
> guix to be a drop in replacement to tools which already allow
> individual users to install and use them without a hassle, like
> Anaconda.
I think we should consider providing a binary tarball produced with
‘guix pack -RR’ instead of just ‘guix pack’. It’s possible to run
“rootless” Guix from there:
https://lists.gnu.org/archive/html/guix-devel/2018-05/msg00139.html
With minor changes to the daemon, we could arrange so that users don’t
have to fiddle with environment variables or anything.
Now, I fear that the typical use case for that is places where user
namespaces aren’t available, which means a degraded experience. (See
the rant at the bottom of
<https://hpc.guix.info/blog/2020/05/faster-relocatable-packs-with-fakechroot/>.)
Thoughts?
Ludo’.
prev parent reply other threads:[~2020-05-24 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 15:25 Propose to distribute a user-only install script, not admin required Josh Marshall
2020-05-16 15:47 ` Tobias Geerinckx-Rice
2020-05-17 2:05 ` Bengt Richter
2020-05-24 19:19 ` Josh Marshall
2020-05-24 20:42 ` 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=877dx112us.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=joshua.r.marshall.1991@gmail.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).