GNU bug report logs - #73294
"guix shell -- anything" does not look for manifests

Previous Next

Package: guix;

Reported by: lgcoelho <at> disroot.org

Date: Mon, 16 Sep 2024 12:42:02 UTC

Severity: normal

To reply to this bug, email your comments to 73294 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#73294; Package guix. (Mon, 16 Sep 2024 12:42:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to lgcoelho <at> disroot.org:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 16 Sep 2024 12:42:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: lgcoelho <at> disroot.org
To: bug-guix <at> gnu.org
Subject: "guix shell -- anything" does not look for manifests
Date: Mon, 16 Sep 2024 14:40:23 +0200
[Message part 1 (text/plain, inline)]
Hello,

Currently, if you have an authorized manifest available and want to run 
some command (for example htop) provided by the manifest, you need to

--8<---------------cut here---------------start------------->8---

$ guix shell
$ htop

--8<---------------cut here---------------end--------------->8---
as supplying a command for guix shell makes it to not look for 
manifests, and instead simply create a empty environment.

--8<---------------cut here---------------start------------->8---

$ guix shell -- htop
guix shell: warning: no packages specified; creating an empty 
environment
guix shell: error: htop: command not found

--8<---------------cut here---------------end--------------->8---

Which doesn't seems a desirable behavior to me. Could we fix it?

Thanks in advance,
Luis
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#73294; Package guix. (Mon, 30 Sep 2024 21:06:02 GMT) Full text and rfc822 format available.

Message #8 received at 73294 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: lgcoelho <at> disroot.org
Cc: 73294 <at> debbugs.gnu.org
Subject: Re: bug#73294: "guix shell -- anything" does not look for manifests
Date: Mon, 30 Sep 2024 23:04:23 +0200
Hi,

lgcoelho <at> disroot.org skribis:

> Currently, if you have an authorized manifest available and want to run 
> some command (for example htop) provided by the manifest, you need to
>
>
> $ guix shell
> $ htop
>
> as supplying a command for guix shell makes it to not look for 
> manifests, and instead simply create a empty environment.
>
>
> $ guix shell -- htop
> guix shell: warning: no packages specified; creating an empty 
> environment
> guix shell: error: htop: command not found
>
> Which doesn't seems a desirable behavior to me. Could we fix it?

This is the documented behavior: ‘manifest.scm’ and ‘guix.scm’ are read
only for interactive use, meaning without ‘--’:

  https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-shell.html

The rationale for it is that non-interactive uses of ‘guix shell’ would
always be self-contained.

This was arguably a very conservative choice but I’m not sure we can
change it at this stage.  Thoughts?

Ludo’.




This bug report was last modified 255 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.