all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: vapnik spaknik <vapniks@yahoo.com>
Cc: 54422@debbugs.gnu.org
Subject: bug#54422: texlive-texmf info manuals are installed outside INFOPATH
Date: Wed, 16 Mar 2022 10:33:28 -0400	[thread overview]
Message-ID: <87v8wearwn.fsf_-_@gmail.com> (raw)
In-Reply-To: <1327774576.610500.1646685784716@mail.yahoo.com> (vapnik spaknik's message of "Mon, 7 Mar 2022 20:43:04 +0000 (UTC)")

Hello,

vapnik spaknik <vapniks@yahoo.com> writes:

> I have texlive installed on a foreign distro at : 
>  /gnu/store/7s4hirky82mfdnmakxswsfb3y5pgg3l2-texlive-texmf-20210325/share/texmf-dist 
>
> within that directory I can see doc/info/latex2e.info
> i.e. the info file for latex2e
> However, I there is no symlink in $GUIX_PROFILE/share/info
> so I cant view it with info, unless I create a symlink myself.
>
> I guess this must be an oversight by the package developers, so I'm reporting it here.

The INFOPATH searh path only looks under the share/info installation
prefix; that's why it doesn't see it.

Perhaps there's a way to configure texlive-texmf to install its info
manuals to share/info instead of share/texmf-dist/doc/info;
alternatively we could, at the level of the texlive-texmf package
definition symlink any share/texmf-dist/doc/info/*.info to share/info/.

Would you like to give it a try?

I'm turning this into a proper bug report, by emailing
"bug-guix@gnu.org".

Thanks for the report!

Maxim




  reply	other threads:[~2022-03-16 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1327774576.610500.1646685784716.ref@mail.yahoo.com>
2022-03-07 20:43 ` texlive doesn't link latex2e.info file in $GUIX_PROFILE/share/info even though it is in the store vapnik spaknik
2022-03-16 14:33   ` Maxim Cournoyer [this message]
2022-04-29 15:25   ` zimoun

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=87v8wearwn.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=54422@debbugs.gnu.org \
    --cc=vapniks@yahoo.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 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.