On Sun, Jan 28, 2018 at 09:24:24AM +0200, Allard Welter wrote: > On Sat, Jan 27, 2018 at 11:45 PM, Ken Moffat <[email protected]> > wrote: > > > Can you get an ID for trac (the wiki), please (ask Bruce) and raise a > ticket > > so I don't forget this ? > > > > At the moment my current systems don't have texlive installed, and I > can't see > > any point in me adding it to them - I'll be throwing them away soon > because we > > will soon be freezing and testing for 8.2. > > It is not a texlive issue. >
In terms of editing the book, if an additional pair of dependencies (tk at compile time, a perl module at runtime) add something that you want, then for editing the book it is a bug against the book's texlive instructions. And I'm not going to add it until I'm using a current system with texlive (so that I can test what I write). What with the current changes in the kernel, new binutils, trying to track down firefox beta in mercurial (*shudders*) and the many other things I've put off until now, I very much doubt that I'll even remember about this unless there is a ticket. > kpsewhich -var-value TEXMFCNF > > gives the correct paths. Evince uses TEXMFCNF from the environment (see > evince-3.26.0/backend/dvi/texmfcnf.c). So now I have > > export TEXMFCNF=`kpsewhich -var-value TEXMFCNF` > > in .bash_profile > When I have texlive installed (not at the moment because my current systems are new, to look at Meltdown and Spectre mitigation, and adding texlive is not worth my time since nothing has changed), my memory says that if texdoc returns a PDF it will be opened in evince because of the MIME type (evince is my default for application/pdf). > > This will just be an optional link to tk, and anm optional runtime > external > > link, ( presumably to http://search.cpan.org/~srezic/Tk-804.034/ ?) so no > big > > deal to add those while we are tagging for 8.2. > > My bad, texdoc points to a script and hence does not need Tk. The perl > module > constructs a gui at runtime. > You said texdoctk, not texdoc. If that needs some random perl module at runtime then the book _could_ point that out. > > FWIW, I've never hear of texdoctk until today, > > There are wonderful things in the texlive documentation! > There are also many archaic things, and other things which are still used in used in certain places despite the availability of things such as xelatex. Spelunking randomly in the documentation can be interesting, but is generally not very productive. Reading the docs when somebody has _suggested_ a tool or package is a different matter. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
