A question about texlive and kpsewhich
by Ilgar from LinuxQuestions.org on (#5KXSK)
Hello,
This is something that came up when I tried to use the LaTeX input feature of Xournal++. It checks the availability of the LaTeX package "standalone" using the output of
Code:kpsewhich standaloneThis fails in Slackware64 14.2 with texlive-2020 from SBo; because the command above has null output although the package is installed. I don't have a -current installation available so I couldn't check if this is the case in -current with the official texlive package.
I can fix this by patching Xournal++ to use
Code:kpsewhich standalone.clsinstead, it then returns
Code:/usr/share/texmf-dist/tex/latex/standalone/standalone.clsand everything works. I am not a TeX expert, but from what I read it seems that this behaviour is related to the way texlive is configured. The maintainer of Xournal++ at SBo suggested sending my patch to upstream, but maybe it is Slackware's texlive that has the non-standard behaviour here. If so, this may affect other software as well (although I know of none, so far).
So here I am bringing this to the attention of our experts here. If it turns out that the issue exists in -current but there is good reason to keep the configuration as-is, then I will try pursuing the matter with the Xournal++ devs.
This is something that came up when I tried to use the LaTeX input feature of Xournal++. It checks the availability of the LaTeX package "standalone" using the output of
Code:kpsewhich standaloneThis fails in Slackware64 14.2 with texlive-2020 from SBo; because the command above has null output although the package is installed. I don't have a -current installation available so I couldn't check if this is the case in -current with the official texlive package.
I can fix this by patching Xournal++ to use
Code:kpsewhich standalone.clsinstead, it then returns
Code:/usr/share/texmf-dist/tex/latex/standalone/standalone.clsand everything works. I am not a TeX expert, but from what I read it seems that this behaviour is related to the way texlive is configured. The maintainer of Xournal++ at SBo suggested sending my patch to upstream, but maybe it is Slackware's texlive that has the non-standard behaviour here. If so, this may affect other software as well (although I know of none, so far).
So here I am bringing this to the attention of our experts here. If it turns out that the issue exists in -current but there is good reason to keep the configuration as-is, then I will try pursuing the matter with the Xournal++ devs.