unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Installing guix packages without root permissions (in HPC environments)
Date: Thu, 19 Jan 2017 06:08:08 +0000	[thread overview]
Message-ID: <20170119060808.GA21181@mail.thebird.nl> (raw)
In-Reply-To: <87eg006o5q.fsf@gnu.org>

On Wed, Jan 18, 2017 at 10:42:09PM +0100, Ludovic Courtès wrote:
> > To fix the prefix restriction there are two routes, one is building
> > Guix itself on a large(r) path, which is the easy route, or write a
> > relocate patcher that can handle the non-zero terminated paths. I
> > think the latter is feasible too. Even at this point the fixed length
> > strategy is useful for most environments - the prefix can be some 40
> > characters long.
> 
> I think the fixed-length restriction is not that bad.  The two
> workarounds above look hacky and super tricky, respectively.  ;-)

Yes. Also I like the fact that we use standard binaries this way that
have been well tested on Guix. If anything goes wrong the problem can
only be the relocation. That makes things tractable.

> Also, if we look at the big picture of non-root usage, this solution
> addresses the most hostile environments: no user namespaces, no
> container-spawning facility, no root guix-daemon, etc.  Granted, these
> hostile environments are still commonplace in HPC, so that’s good.  :-)

Yes, if this works it will be rather good and create awareness for
Guix. Another use-case may be firefox plugins - or other software that
wants to install binaries.  Maybe they'll wake up to guix too. From a
developers point of view Guix is awesome because it creates
reproducible environments that we can develop against. What more do we
need ;). We are now using it for a bug hunt on sambamba which only
segfaults on particular HPC setups. The guix relocatable installer is
going to help.

I'll take the installer to the level that we can do one-step installs
and provide a few packages for download to reach out to certain
communities (dlang and elixir come to mind).

Pj.
-- 

  reply	other threads:[~2017-01-19  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17  9:15 Installing guix packages without root permissions (in HPC environments) Pjotr Prins
2017-01-17 12:48 ` Hartmut Goebel
2017-01-18 21:42 ` Ludovic Courtès
2017-01-19  6:08   ` Pjotr Prins [this message]
2017-01-19 11:55     ` Ludovic Courtès
2017-01-19 13:12       ` Pjotr Prins
2017-01-21  7:16       ` 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=20170119060808.GA21181@mail.thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).