<div dir="ltr"><div><div>Hi,<br><br></div>it depends on your configuration whether you need mktexlsr or not. The paths are configured in texmf.cnf. If the path begins with two exclamation marks, only the ls-R file is used for locating the file. This means that mktexlsr is needed. If the path does not have exclamation marks which is the case of $TEXMFHOME, ls-R files are not used. It is described in detail in the documentation of kpathsea, I do not remember the exact details. The location of $TEXMFHOME can be found by kpsewhich. So if you wish to provide the files for non-experts, it would be better to provide a script which will first locate itself, then locate $TEXMFHOME, create the directories (if they do not exist) and create the symlink. The command you need is:<br><br>kpsewhich -var-value TEXMFHOME<br><br></div>Variables TEXMF and TEXMFDBS contain the paths with exclamation marks. If the path is here with the exlamation marks, you must call mktexlsr after creation of the symlink.<br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Zdeněk Wagner<br><a href="http://ttsm.icpf.cas.cz/team/wagner.shtml" target="_blank">http://ttsm.icpf.cas.cz/team/wagner.shtml</a><br><a href="http://icebearsoft.euweb.cz" target="_blank">http://icebearsoft.euweb.cz</a></div></div>
<br><div class="gmail_quote">2018-04-13 8:58 GMT+02:00 Urs Liska <span dir="ltr"><<a href="mailto:lists@openlilylib.org" target="_blank">lists@openlilylib.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi all,</p>
<p>there's an issue I've come across occasionally, and I'd like to
clarify this once and for all ...</p>
<p>I have installed texlive-full on Debian, actually I've dragged
this along through a number of installations while keeping my home
partition, so maybe there's something I have done in the past to
make things "work for me".</p>
<p>My $TEXMFHOME is ~/texmf, and I have a number of custom packages
I use and make available through this $TEXMFHOME.</p>
<p>However, since I maintain my stuff with Git I prefer having the
actual code sitting below ~/git/latex/<packages>, and I have
~/texmf/tex/latex/latex-git as a symlink to ~/git/latex.</p>
<p>Through this LaTeX finds any resources in and below ~/git/latex,
which is what I want - so it "works for me". It also has always
worked when I started using a fresh distribution (but always
Debian-based distros if that matters).</p>
<p>The problem is that collaborators don't always seem to be able to
follow instructions like:</p>
<ul>
<li>look for or create and cd into ~/texmf/tex/latex</li>
<li>create a symlink with<br>
ln -s /path/to/our/project/latex-<wbr>resources</li>
<li>try compiling the document</li>
</ul>
<p>I read about having to use texhash and/or mktexlsr - once or
after every changes to ~/texmf - but I don't seem to have to do
that on my computer. Is the behaviour of finding packages in the
"home" tree depending on the LInux distro or the way how TeXLive
is installed (manual/package)? Do the differen LaTeX engines
behave differently in this regard?<br>
</p>
<p>Currently I have a contributor using Gentoo Linux with
texlive-full installed from the distro's repositories. He has
added the symlink to our project's latex directory but when
compiling (with lualatex filename) it chokes upon not finding the
document class (in that directory).</p>
<p>I would really like to know what steps have to be taken and if
they differ in any way depending on the environment. It's not only
that I need to get this contributor up and running, but I need to
write a CG that will free me from unnecessary hassles with future
contributors.</p>
<p>Thanks for any clarification<span class="HOEnZb"><font color="#888888"><br>
Urs<br>
</font></span></p>
</div>
</blockquote></div><br></div>