[tex-live] install problem, texlive-2017

George N. White III gnwiii at gmail.com
Fri Mar 16 13:37:14 CET 2018


On 15 March 2018 at 18:14, <karl at aspodata.se> wrote:

> George N. White III:
> > On 15 March 2018 at 06:49, <karl at aspodata.se> wrote:
> >
> > > As user texlive.texlive I installed texlive2017, but I have trouble
> > > getting it to work.
> > >
> > > E.g.:
> > > $ kpsewhich article.cls
> > > $ find . -name article.cls
> > > ./2017/texmf-dist/tex/latex/base/article.cls
> > > $ pwd
> > > /usr/local/texlive
> > > $
> > >
> > > any ideas ?
> > >
> > > =======================
> > >  I have added:
> > > MANPATH=$MANPATH:/usr/local/texlive/2017/texmf-dist/doc/man
> > > INFOPATH=$INFOPATH:/usr/local/texlive/2017/texmf-dist/doc/info
> > > PATH=$PATH:/usr/local/texlive/2017/bin/x86_64-linux
> > >  [...]
> >
> > OP Karl  has:
> >
> > $ ls -l /usr/local
> > lrwxrwxrwx 1 root root 13 Jan 23  2016 /usr/local -> ../home/local
> >
> > TL is designed so you can put it anywhwere in your filesystem
> > and have it work by adjusting the PATH variable.  Is there any
> > pressing reason to use /usr/local/texlive over /home/local/texlive?
>
> No, it's just that I have /usr ro, and most configure prefixes are
> /usr/local.
>
> > OP Karl -- can you try:
> >
> >   PATH=/home/local/texlive/2017/bin/x86_64-linux:$PATH
>
> Ok, rearranged thoose three PATHs above.
>
> $ which kpsewhich
> /usr/local/texlive/2017/bin/x86_64-linux/kpsewhich
> $ kpsewhich article.cls
> $
>
> Same result.
>
> > It could be instructive to play around with the kpsewhich debugging
> > options.
>
> $ kpsewhich -debug 2 article.cls
> kdebug:db:init(): using db file /home/local/texlive/texmf-local/ls-R.
> kdebug:db:init(): using db file /home/local/texlive/2017/
> texmf-config/ls-R.
> kdebug:db:init(): using db file /home/local/texlive/2017/texmf-var/ls-R.
> kdebug:db:init(): using db file /home/local/texlive/2017/texmf-dist/ls-R.
> kdebug:/home/local/texlive/texmf-local/ls-R: 29 entries in 28 directories
> (0 hidden).
> kdebug:ls-R hash table:64007 buckets, 18 nonempty (0%); 29 entries,
> average chain 1.6.
> kdebug:/home/local/texlive/2017/texmf-config/ls-R: 2 entries in 1
> directories (0 hidden).
> kdebug:ls-R hash table:64007 buckets, 18 nonempty (0%); 31 entries,
> average chain 1.7.
> kdebug:/home/local/texlive/2017/texmf-var/ls-R: 148 entries in 35
> directories (0 hidden).
> kdebug:ls-R hash table:64007 buckets, 142 nonempty (0%); 179 entries,
> average chain 1.3.
> kdebug:/home/local/texlive/2017/texmf-dist/ls-R: 167171 entries in 12327
> directories (0 hidden).
> kdebug:ls-R hash table:64007 buckets, 54321 nonempty (84%); 167350
> entries, average chain 3.1.
> $ grep -B4 ^article.cls `kpsewhich -debug 2 article.cls 2>&1 | grep
> db:init | grep dist | sed -e 's/.*file//; s/\.$//;'`
> ./tex/latex/base:
> alltt.sty
> ansinew.def
> applemac.def
> article.cls
> $
>
> So, kpsewhich is using a db file where the answer is.
> Is there any other debug num's I should try ?
>

I use a symbolic link, e. g.:

    $ ls -l /usr/local/texlive/current
    lrwxrwxrwx 1 gwhite bod 10 Jun  4  2017 /usr/local/texlive/current ->
svn/Master

but kpsewhich always reports the real path, e.g., "
/usr/local/texlive/svn/Master".

I've forgotten the details of how kpsewhich deals with full paths.  I think
it constructs a path from the real location of the ls-R file and the subpath
from the ls-R file.    Maybe it expects /opt/local and rejects results from
/home/local.   Does "texconfig conf" have all "/home/local" paths or
are some "/opt/local"?

Have a look at the results for debug values 32 and 64.

-- 
George N. White III
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20180316/c2126cd1/attachment.html>


More information about the tex-live mailing list