Hi, I have some Texlive observations and questions that I encountered when I built texlive pass1 from source using BLFS instructions.
First, couple of questions, mainly for Ken - I apologize if this has
been answered somewhere, I wasn't following the large Texlive thread
that happened not so long ago:
Why is '/opt/texlive/2014' used as a prefix? Why not simply
/opt/texlive, or if year is a must, /opt/texlive2014?
Why is '--bindir=/opt/texlive/2014/bin/$TEXARCH' specified? Why is it
needed to specifiy an architecture there? For compatibility with binary
installer which iirc does the same? Or is there something else that
requires it to be like this?
Why is the following command used tar -xf texlive-20140525-texmf.tar.xz
-C /opt/texlive/2014 --strip-components=1 ? The current directory should
be: "${SOURCEDIR}/texlive-20150525-source/build", which would make this
command invalid iirc. I suppose it needs ../../ before the tarball name
if we are to follow the conventions used elsewhere.
Now couple of observations:
libpaper is listed as a recommended dep, yet no --with-system-libpaper
switch is present like for other recommended packages. Intentional or
nothing in this pass uses it?
For the optional dependencies, there's a sentence that says "The source
ships with its own versions of several libraries which are either not
under active development, or only used for limited functionality." with
libgd listed there. I don't think it's inactive as the most recent
version is from last year and it can also be used by PHP instead of its
bundled one. Latest t1lib is indeed a bit rusty, but it can be used at
least by evince and maybe one or two moe packages.
The following text is written above the texmf tarball: "Because of the
size of this package, it is unlikely to be mirrored by BLFS mirrors. In
case of difficulty, go to http://www.ctan.org/mirrors/ to find a
more-accessible mirror." The URL is written as plain text. It would be
nice if it was "clickable".
Alternatively, you may have seen my mail @ blfs-support mailing list. No
mirror listed on that page contains the texmf tarball as-is or I have
been unable to find it. If it's indeed there, a small clarification
about the path to it could be useful.
The texmf tarball contains a lot of documentation which may not be
useful to some (including myself) that takes _a lot_ of space (~1.4-1.6
GB). Since not everybody would want to install the documentation since
it takes that much space and it's available online, I suppose the
following command could be used to prevent "doc" (and "sources")
directories to be installed, saving at least ~1.6 GB of space. The fonts
directory takes a lot of space too. Some fonts may be ommited, but I am
not sure which ones. Anyways, the command I used to ommit source and
documentation extraction was: tar --exclude=*/texmf-dist/doc
--exclude=*/texmf-dist/source --strip-components=1 -xf
texlive-20140525-texmf.tar.xz ...
Last, but not the least. I have an issue. I went and installed it into
/usr, but can't get some kind of catalog to generate itself, this the
entire install becomes useless. The following output is from pdflatex:
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014 - BLFS)
(preloaded format=pdflatex)
restricted \write18 enabled.
kpathsea: Running mktexfmt pdflatex.fmt
/usr/bin/mktexfmt: line 398: //texmf-dist/texconfig/tcfmgr: No such file
or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `pdflatex.fmt'!
The //texmf-dist is what's reported by kpsewhich -var-value TEXMFDIST
which should be /usr/share/texmf-dist. The build script I used is
available at:
https://raw.githubusercontent.com/elkrejzi/system-management/master/buildscripts/buildtexlive
kpsewhich appears to be looking in /usr/share/texmf-dist/web2c/texmf.cnf
for details, but there's only a reference to
TEXMFROOT = $SELFAUTOPARENT
TEXMFDIST = $TEXMFROOT/texmf-dist
However, I have no idea where SELFAUTOPARENT is being set and what it is
being set to.
Cheers.
--
Note: My last name is not Krejzi.
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
