From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 34859-done@debbugs.gnu.org
Subject: bug#34859: [PATCH] pack: "-RR" produces PRoot-enabled relocatable binaries.
Date: Fri, 15 Mar 2019 23:34:53 +0100 [thread overview]
Message-ID: <87bm2b22cy.fsf@gnu.org> (raw)
In-Reply-To: <87wol015uk.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 15 Mar 2019 17:04:51 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> * gnu/packages/aux-files/run-in-namespace.c (exec_with_proot): New
>> function.
>> (main): When 'clone' fails, call 'rm_rf'.
>> [PROOT_PROGRAM]: When 'clone' fails, call 'exec_with_proot'.
>> * guix/scripts/pack.scm (wrapped-package): Add #:proot?.
>> [proot]: New procedure.
>> [build]: Compile with -DPROOT_PROGRAM when PROOT? is true.
>> * guix/scripts/pack.scm (%options): Set the 'relocatable?' value to
>> 'proot when "-R" is passed several times.
>> (guix-pack): Pass #:proot? to 'wrapped-package'.
>> * tests/guix-pack-relocatable.sh: Use "-RR" on Intel systems that lack
>> user namespace support.
>> * doc/guix.texi (Invoking guix pack): Document -RR.
>
> This is great!
>
> So, the only downside to using “-RR” is that it’s 1MB heavier than “-R”
> due to the included proot-static?
Yes! But note that our ‘proot-static’ package currently fails to build
on ARM.
> Neat!
Pushed as 99aec37a78e7be6a591d0e5b7439896d669a75d1, thanks!
Ludo’.
prev parent reply other threads:[~2019-03-15 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 16:10 [bug#34859] [PATCH] pack: "-RR" produces PRoot-enabled relocatable binaries Ludovic Courtès
2019-03-15 13:41 ` Ludovic Courtès
2019-03-15 14:24 ` Julien Lepiller
2019-03-15 14:44 ` Ludovic Courtès
2019-03-15 16:04 ` Ricardo Wurmus
2019-03-15 22:34 ` 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=87bm2b22cy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34859-done@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).