From: "Ludovic Courtès" <ludo@gnu.org>
To: Distopico <distopico@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Guix CLI options through manifest.scm or guix.scm
Date: Thu, 14 Sep 2023 11:38:22 +0200 [thread overview]
Message-ID: <875y4df629.fsf@gnu.org> (raw)
In-Reply-To: <87pm38bas8.fsf@riseup.net> (distopico@riseup.net's message of "Sun, 27 Aug 2023 13:25:57 -0500")
Hi,
Distopico <distopico@riseup.net> skribis:
> Is it possible to define/express CLI options from manifest.scm or
> guix.scm? For example, I have
>
> ```
> guix shell \
> -m manifest.scm \
> --container -F -N -P \
> --share=/opt/android-sdk \
> --share=$HOME/.android/avd \
> --share=$HOME/.gradle/ \
> --preserve='^DISPLAY$' \
> --preserve='^XAUTHORITY$' \
> --preserve='^DBUS_' \
> --expose=$XAUTHORITY \
> --expose=/var/run/dbus
> ```
There are two things relevant to ‘guix shell’: (1) what packages go
inside the environment, and (2) how the environment is built (container
vs. pure, networking or not, etc.).
The manifest only takes care of #1.
We need a non-CLI way to express #2. I don’t think manifests are a good
fit for that; perhaps we need a new <environment> abstraction, which
might mean we need a new ‘environment.scm’ file or similar.
Anyhow, I agree that something’s missing here.
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-09-14 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 18:25 Guix CLI options through manifest.scm or guix.scm Distopico
2023-08-27 19:59 ` Liliana Marie Prikler
2023-08-29 18:43 ` Distopico
2023-08-29 20:05 ` Distopico
2023-09-14 9:38 ` Ludovic Courtès [this message]
2023-09-19 0:12 ` Distopico
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=875y4df629.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=distopico@riseup.net \
--cc=guix-devel@gnu.org \
/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).