[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tracking and inspecting how Guix changes over time
From: |
Ricardo Wurmus |
Subject: |
Re: Tracking and inspecting how Guix changes over time |
Date: |
Wed, 13 Feb 2019 15:37:01 +0100 |
User-agent: |
mu4e 1.0; emacs 26.1 |
Christopher Baines <address@hidden> writes:
>> For an automated system like this, it’s a bit different, so using a
>> container makes a lot of sense. I’d suggest having an option directly
>> in (guix inferior) to allow users to choose whether to run an inferior
>> in separate name spaces. WDYT?
>
> That sounds great, I'm not quite sure how to make it happen though...
>
> So inferior-pipe in (guix inferior) uses open-pipe*. The root of the
> Linux container code in Guix looks to be run-container (gnu build
> linux-container).
You can use “call-with-container”, which runs a thunk inside a container.
--
Ricardo