From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Propose to distribute a user-only install script, not admin required
Date: Sat, 16 May 2020 17:47:39 +0200 [thread overview]
Message-ID: <87imgvop9g.fsf@nckx> (raw)
In-Reply-To: <CAFkJGRcqFGi9sQL7GLwBEVr_0YQ9THGfX9-VxgpTxgcvTaJr1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Josh,
Josh Marshall 写道:
> 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.
An old but classic place to start is [0] which explains some of
the problems & trade-offs, and illustrates an approach that may or
may not still work today.
My subjective impression was that this used to be more of a big
deal (i.e. a few years ago) than it is now. I don't know if it's
less of a problem these days, or people gave up on asking, or
perhaps I'm not in the right channels to hear the clamouring.
Part of me thanks you for bringing this up again. I'm interested
to see where it goes.
Another part of me fears that ‘rootless Guix’ is just the perfect
excuse for misguided admins to give their users a pale and
flavourless Guix experience. It would rather taint the brand.
Kind regards,
T G-R
[0]:
https://github.com/pjotrp/guix-notes/blob/master/GUIX-NO-ROOT.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-16 15:48 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 [this message]
2020-05-17 2:05 ` Bengt Richter
2020-05-24 19:19 ` Josh Marshall
2020-05-24 20:42 ` 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=87imgvop9g.fsf@nckx \
--to=me@tobias.gr \
--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).