From: Zhu Zihao <all_but_last@163.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: A public Lisp programming interface provide feature like `guix environment --container`
Date: Wed, 04 Nov 2020 18:05:26 +0800 [thread overview]
Message-ID: <864km55teh.fsf@163.com> (raw)
In-Reply-To: <33db285c56516bac910112344b7c9766221bdaf3.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Leo Prikler writes:
> launch-environment/container still assumes the command to be a shell
> script, which I think is not quite what you want. You probably want to
> take a look at call-with-container from (guix build linux-container) or
> child-hurds.
I just read the source code of call-with-container. IMO, it just run
code in container, without any settings. It's quite inconvenient for my
usage. For example: I have to setup mount binding of my package closure manually.
> I currently don't know of any procedure, that "directly" invokes Scheme
> code through Guix environments, so you'd have to build that on your
> own. However, given that your stated goal is to port container entry
> scripts [I read this as "the script called by the container at entry"]
> to Guile, would it not make sense to have
>
> (guix-environment [ENVIRONMENT OPTIONS] "--" "guile" "entry.scm")
>
> WDYT?
>
> Regards, Leo
Hmmm, maybe this is the solution, tho it's not very very elegant.
--
Retrieve my PGP public key: https://meta.sr.ht/~citreu.pgp
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
next prev parent reply other threads:[~2020-11-04 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 7:38 A public Lisp programming interface provide feature like `guix environment --container` Leo Prikler
2020-11-04 10:05 ` Zhu Zihao [this message]
2020-11-04 10:23 ` Leo Prikler
2020-11-04 10:36 ` Zhu Zihao
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 3:49 Zhu Zihao
2020-11-06 9:41 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864km55teh.fsf@163.com \
--to=all_but_last@163.com \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.