[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#36668: closed ([PATCH 0/1] Add 'eval/container')

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#36668: closed ([PATCH 0/1] Add 'eval/container')
Date: Fri, 19 Jul 2019 09:56:02 +0000

Your message dated Fri, 19 Jul 2019 11:55:29 +0200
with message-id <address@hidden>
and subject line Re: [bug#36668] [PATCH 0/1] Add 'eval/container'
has caused the debbugs.gnu.org bug report #36668,
regarding [PATCH 0/1] Add 'eval/container'
to be marked as done.

(If you believe you have received this mail in error, please contact

36668: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36668
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH 0/1] Add 'eval/container' Date: Mon, 15 Jul 2019 16:21:26 +0200
Hello Guix!

This adds ‘eval/container’, which can be used to implement things that
are almost derivation (pure computational processes), but not quite:
processes that produce side effects, that need to access the daemon,
or that need to talk over the network.

It doesn’t have any users currently.  Guix-Jupyter-Kernel will probably
use it (to spawn proxied kernels in isolated environments), and I think
Ricardo had a use case for it in GWL too.

What do people think?

I wonder if we should target ‘run-in-container’ instead of
‘call-with-container’, or maybe both.  It’s also a bit troubling
that ‘eval/container’ returns an exit status instead of the evaluation
result, but I think it has to be this way, more or less.


Ludovic Courtès (1):
  linux-container: Add 'eval/container'.

 gnu/system/linux-container.scm | 49 ++++++++++++++++++++++++++++++++-
 tests/containers.scm           | 50 ++++++++++++++++++++++++++++++++++
 2 files changed, 98 insertions(+), 1 deletion(-)


--- End Message ---
--- Begin Message --- Subject: Re: [bug#36668] [PATCH 0/1] Add 'eval/container' Date: Fri, 19 Jul 2019 11:55:29 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]