unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [Non-root Guix]: Unable to build guix
Date: Sun, 05 May 2019 10:03:00 +0200	[thread overview]
Message-ID: <87r29dxr9n.fsf@elephly.net> (raw)
In-Reply-To: <87h8a9vini.fsf@netris.org>


Mark H Weaver <mhw@netris.org> writes:
[…]
> Ricardo Wurmus <rekado@elephly.net> writes:
[…]
>> I see.  Unfortunately you will end up having to compile everything from
>> source, C library, GCC,… — all of it.  When using a different store
>> location it is impossible to use pre-built binaries, unfortunately.
>
> If one is able to obtain write access to any directory accessible via an
> absolute path name of no more than 10 bytes, e.g. "/tmp/xxxxx",
> "/var/tmp/x", "/home/xx/x", or possibly even "/home/xxxx" or
> "/home/xxx", then it may be possible to avoid compiling everything from
> source code.

I think it’s worth supporting prefix rewrites. On a system where the
user does not have root access and no user namespaces the daemon will
not be able to build anything in isolation.  The best case here is to
*only* use substitutes and to limit the local operations to rewriting
the prefix.

This requires modifying store items before unpacking them.  Since root
is not involved this should only ever affect one user.

--
Ricardo

  reply	other threads:[~2019-05-05  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 20:15 [Non-root Guix]: Unable to build guix rohit yadav
2019-05-02 20:33 ` Ricardo Wurmus
2019-05-02 21:14   ` rohit yadav
2019-05-02 21:37     ` Ricardo Wurmus
2019-05-02 22:13       ` rohit yadav
2019-05-02 21:46     ` Ricardo Wurmus
2019-05-02 22:17       ` rohit yadav
2019-05-04  6:14       ` Chris Marusich
2019-05-05  0:39       ` Mark H Weaver
2019-05-05  8:03         ` Ricardo Wurmus [this message]
2019-05-02 20:34 ` Ricardo Wurmus
2019-05-02 21:17   ` rohit yadav

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=87r29dxr9n.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).