From: Rowaaaaan <Rowaaaaan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tlmgr is broken because Perl can't find TLConfig.pl
Date: Tue, 29 Nov 2022 11:08:56 +0100 [thread overview]
Message-ID: <20221129100856.7vA6uUcPA-Vs8vAvp2EVCKyIpWLMdBIfODDds5uYeZ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40830@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
New comment by Rowaaaaan on void-packages repository
https://github.com/void-linux/void-packages/issues/40830#issuecomment-1330387012
Comment:
I did some digging into the script myself to see what the problem was, since I'm not sure if this is a texlive issue or a Perl issue.
From line 41:
```perl
BEGIN {
# make subprograms (including kpsewhich) have the right path:
$bindir = $Master;
$ENV{"PATH"} = "$bindir:$ENV{PATH}";
$::installerdir = $Master; # for config.guess et al., see TLUtils.pm
# make Perl find our packages first:
unshift (@INC, "$Master/tlpkg");
unshift (@INC, "$Master/texmf-dist/scripts/texlive");
...
use TeXLive::TLConfig;
use TeXLive::TLPDB;
```
The error occurs at line 61, where tlmgr uses the TLConfig:
```perl
use TeXLive::TLConfig;
```
The confusing part is how the error says that it can't find TLConfig @INC, which is at `/usr/share/texmf-dist/scripts/texlive`, despite the fact that `TLConfig.pm` _is_ in `/usr/share/texmf-dist/scripts/texlive/TeXLive`
So, I tried hardcoding the absolute path to `TLConfig.pm`, by adding the line:
```perl
unshift (@INC, "$Master/texmf-dist/scripts/texlive/TeXLive/TLConfig.pm");
```
and `tlmgr` still throws the exact same error
next prev parent reply other threads:[~2022-11-29 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 9:55 [ISSUE] " Rowaaaaan
2022-11-29 10:08 ` Rowaaaaan [this message]
2022-11-29 13:37 ` nsajko
2022-11-29 13:48 ` classabbyamp
2022-12-14 15:45 ` tornaria
2023-07-04 22:32 ` [ISSUE] [CLOSED] " Rowaaaaan
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=20221129100856.7vA6uUcPA-Vs8vAvp2EVCKyIpWLMdBIfODDds5uYeZ4@z \
--to=rowaaaaan@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).