all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Domagoj Stolfa <domagoj.stolfa@gmail.com>
To: 47830@debbugs.gnu.org
Subject: bug#47830: texlive-bin: perl utilities runtime failure
Date: Fri, 16 Apr 2021 21:49:42 +0100	[thread overview]
Message-ID: <30b03ebc-3fd2-a99b-9ccd-f7c7b2d97d44@gmail.com> (raw)

Hello:


I've been trying to use the texlive distribution from guix, but noticed 
a particular issue with a few of the texlive-bin utilities, namely 
latexindent and latex-git-log. There may be more that suffer this issue.


Following the discussion on IRC -- when texlive-bin gets installed, it 
is split up from texlive-texmf. This results in the perl utilities 
having the wrong @INC path, namely they end up with (using latexindent 
as an example):


/gnu/store/jr9czrjx7slnda355xfmbv6hkkdpl5qi-texlive-bin-20190410/share/texmf-dist/scripts/latexindent 



rather than the expected path containing their includes:


/gnu/store/cqfhb3hfvyxacn200n0jxkf3wq8328yq-texlive-texmf-20190410/share/texmf-dist/scripts/latexindent 



This results in a runtime error which looks a bit like "Can't locate 
LatexIndent/Document.pm in @INC (you may need to install the 
LatexIndent::Document module)". A simple fix for this would be to 
migrate texlive-scripts from texlive-bin to texlive-texmf (in tex.scm) 
or to perhaps merge texlive-bin and texlive-texmf. However, since I 
haven't done much with guix outside of just using it, I don't really 
know what the best approach would be. Perhaps it would make sense to 
discuss what the best approach would be here?


Thanks!


-- 

Domagoj





             reply	other threads:[~2021-04-17  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 20:49 Domagoj Stolfa [this message]
2021-04-19  2:29 ` bug#47830: texlive-bin: perl utilities runtime failure Maxim Cournoyer

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=30b03ebc-3fd2-a99b-9ccd-f7c7b2d97d44@gmail.com \
    --to=domagoj.stolfa@gmail.com \
    --cc=47830@debbugs.gnu.org \
    /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.