From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 66757@debbugs.gnu.org
Subject: bug#66757: missing INFOPATH for some packages (Git, Coreutils)
Date: Fri, 27 Oct 2023 02:32:09 +0000 [thread overview]
Message-ID: <87cyx023to.fsf@protonmail.com> (raw)
In-Reply-To: <87fs1xhkgf.fsf@gmail.com>
Hello,
On Thu, Oct 26, 2023 at 10:11 AM, Simon Tournier wrote:
> Hi,
>
> Is it expected
>
> $ guix shell -C git coreutils
> [env]$ ls $GUIX_ENVIRONMENT/share/info
> coreutils.info.gz dir git.info.gz gitman.info.gz
>
> /tmp/some-dir [env]$ exit
Well there's no info-reader right? So doing "info git" errors with no
"info" found.
> $ guix shell -C git coreutils --search-paths
> export PATH="/gnu/store/jigy78ai2asmgwhxpxzq2dhqhqi8c4p6-profile/bin${PATH:+:}$PATH"
> export GIT_EXEC_PATH="/gnu/store/jigy78ai2asmgwhxpxzq2dhqhqi8c4p6-profile/libexec/git-core"
>
> ? I was expecting an INFOPATH in the search path.
>
If you add info-reader to the packages I get an INFOPATH search-path
(and of course then an info command is available and works).
> Well, it appears to me a bug but if I am missing something, feel free to
> point me what :-) and then close.
>
>
> Cheers,
> simon
So I think it is just that you didn't have the "consumer" of the
search-path, the package info-reader, in the profile. That seems like
the expected functionality of search-path but maybe I'm missing
something? Not closing in case it is me not you :)
(as an aside, I never remember the package for the same thing with
man...)
John
next prev parent reply other threads:[~2023-10-27 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:11 bug#66757: missing INFOPATH for some packages (Git, Coreutils) Simon Tournier
2023-10-27 2:32 ` John Kehayias via Bug reports for GNU Guix [this message]
2023-10-27 9:08 ` Simon Tournier
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=87cyx023to.fsf@protonmail.com \
--to=bug-guix@gnu.org \
--cc=66757@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=zimon.toutoune@gmail.com \
/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).