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!