From: Distopico <distopico@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix CLI options through manifest.scm or guix.scm
Date: Mon, 18 Sep 2023 19:12:16 -0500 [thread overview]
Message-ID: <87r0mvc96v.fsf@riseup.net> (raw)
In-Reply-To: <875y4df629.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
On 2023-09-14, Ludovic Courtès <ludo@gnu.org> wrote:
> 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’.
Aren't there many variations/types of files? But still, it would be
ideal to configure it. Perhaps 'envrc.scm' could be another option.
Best!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
prev parent reply other threads:[~2023-09-19 0:13 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
2023-09-19 0:12 ` Distopico [this message]
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=87r0mvc96v.fsf@riseup.net \
--to=distopico@riseup.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.