|
From: | Maxime Devos |
Subject: | bug#57467: 'guix shell' does not honor default behavior when given a specific command to run |
Date: | Mon, 5 Sep 2022 21:53:20 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 |
On 05-09-2022 15:06, Ludovic Courtès wrote:
The main difficulty here is that, should we eventually decide to change behaviors, we’ll have to devise a migration timeline etc. (As an example, we chose to keep ‘guix environment’ until at least May 2023; all this must take time if we want to avoid breaking user workflows.) Thoughts?
"guix shell" is for making packages available in the environment. Currently, "guix shell -- foobar" does not make any packages available -- it's effectively a no-op except for setting GUIX_ENVIRONMENT. As such, I expect nobody is actually relying on "guix shell -- foobar" to not load guix.scm or manifest.scm and I think that if we go for this change, the migration timeline can be rather minimal.
Greetings, Maxime.
OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |