From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: guix-devel@gnu.org
Subject: Re: Hacks to install Guix packages without root
Date: Fri, 27 Oct 2017 08:53:51 +0200 [thread overview]
Message-ID: <63a4cea2-1518-81cb-00aa-27e6fcfa3021@fastmail.net> (raw)
In-Reply-To: <874lqlmvjn.fsf@elephly.net>
On 26/10/2017 23:46, Ricardo Wurmus wrote:
> How about an extension of “guix pack” that will rewrite the /gnu/store
> references to a user-provided directory before bundling things up in a
> tarball? I’d *really* like to be able to just use the tarball bundle
> “guix pack” produces by default, but currently deploying it requires
> root access or proot shenanigans at runtime.
That would be nice indeed as a deployment option. In particular for
distributing binaries to less experienced users.
On 27/10/2017 02:48, Ludovic Courtès wrote:
> The tarballs could include proot-static and another statically-linked
> program that essentially tries to call unshare(2). Would that make
> sense?
That's perhaps good enough as well. Suggestion: try to write the user
instructions for deploying these tarballs first, and pick the method
that is easiest to describe.
I see basically two usage scenarios. One is a form of software
installation: users download a tarball, follow the instruction
procedure, and than have some additional commands in their PATH. The
other scenario is the creation of a somewhat isolated environment, with
users wanting a shell for working in just that environment. For that
second scenario, proot is probably just fine, but I am less convinced
about the first one.
Konrad.
next prev parent reply other threads:[~2017-10-27 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 21:46 Hacks to install Guix packages without root Ricardo Wurmus
2017-10-27 0:48 ` Ludovic Courtès
2017-10-27 8:27 ` Pjotr Prins
2017-10-31 14:19 ` Dave Love
2017-11-03 11:54 ` Pjotr Prins
2017-11-06 15:03 ` Dave Love
2017-11-06 16:13 ` Pjotr Prins
2017-10-27 6:53 ` Konrad Hinsen [this message]
2017-10-27 8:17 ` Pjotr Prins
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=63a4cea2-1518-81cb-00aa-27e6fcfa3021@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.org \
/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).