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:36:25 +0800 [thread overview]
Message-ID: <86lffh2yty.fsf@163.com> (raw)
In-Reply-To: <42ddcb59882ded6c18da226c56bec7e6e224801a.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Leo Prikler writes:
> For the record, what you do want is something à la
> (call-in-container-environment THUNK MANIFEST . KWARGS)
> where manifest is the Guix environment manifest, THUNK is a procedure
> to call with 0 arguments and KWARGS is a list of options for things you
> might want to set up, e.g. just the GUIX_ENVIRONMENT variable or more
> than that.
>
> Is that about right?
>
> Regards, Leo
Yes, that's what I want. KWARGS may accept something like user-mappings,
network?, namepsaces etc. like `launch-environment/container`. So I can
create container entry script for different executable in batch with
more confidence in code reuse. It's ugly to
concatenate string argument (For example: `(string-append "--expose="
xxxx "=" yyy)`) when I want to reuse some path variable.
--
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:37 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
2020-11-04 10:23 ` Leo Prikler
2020-11-04 10:36 ` Zhu Zihao [this message]
-- 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
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=86lffh2yty.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 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).