FYI. This is not directly usable in BLFS, I think, but someone can find it
helpful.
Here is an example of the build meant to be as close to the default
procedure as possible. It needs neither patching nor relinking of the
binaries. I use BLFS setup command sequence in the end.
./configure \
--prefix=/opt/texlive/texmf \
--disable-largefile \
--disable-missing \
--with-banner-add='/MiX'
make
make DESTDIR=`pwd`/inst install-strip
mkdir -pv /opt/texlive/texmf/bin
mv -v inst/opt/texlive/texmf/bin/*/* /opt/texlive/texmf/bin/
tar xf ../texlive-20100722-texmf.tar.xz \
-C /opt/texlive --strip-components=1
Resulting layout is this:
/opt/texlive/texmf/bin/
/opt/texlive/texmf/web2c/texmf.cnf
/opt/texlive/texmf-dist/scripts/
/opt/texlive/texmf-config/
/opt/texlive/texmv-var/
/opt/texmf-local/
/opt/texmf.cnf
NOTES
1.) All local changes are supposed to be done outside the main tree, in
/opt/texmf-local and related /opt/texmf.cnf, which makes perfect sense. In
the above installation, the second texmf.cnf is not needed and can be
empty or omitted.
If texmf-local/ is moved to /opt/something, as in the current BLFS,
variable TEXMFLOCAL should be redefined in the local texmf.cnf file (only
that variable, there will be just one line in the file then). No changes
in the default web2c/texmf.cnf are allowed.
2.) Only binaries (and libraries, if built with --enable-shared) are
installed first. According to TUG, data files installed from
texlive-*-sources are useless. This doesn't mean they cannot be correct,
just that devs don't care if they are.
3.) --disable-largefile is the default argument in TUG builds (currently
processing of large files >2GB is not reliable).
4.) --disable-missing breaks the build if any required package is missing.
---
Alex.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
