Ken Moffat wrote:
I'm getting ready to add the *real* from-source texlive build to
the book, using the texmf tarball to provide 3.6GB of scripts and
docs. But I've got a couple of questions:
1. Where do we encourage people to keep their source tarballs ? I'm
guessing /sources but I might be wrong.
For BLFS packages, I use /usr/src/pkgname.
The reason for that question is that the install consists of
mkdir -pv /opt/texlive/2014
cd /opt/texlive/2014
tar -xf /path/to/texlive-20140525-texmf.tar.xz --strip-components=1
I suggest just using that, perhaps with some highlighting.
2. When building texlive without a pre-existing tex installation,
the build has to be done twice: first time, a few parts (asy, xindy)
require various tex programs and cannot be built, also the install
is slightly different; second time (with the tex progs on $PATH) it
can all be built as we currently do. Of course die-hard TeX purists
might shun asy and xindy. For them, the smaller install may
suffice.
That's fine as long as it's explained.
I was originally going to put the multiple variants all in one page
[ not uncommon for BLFS, but hard to follow ], but I think it might
be clearer if I separated the first partial build to its own page,
somewhat like how LFS has two passes of binutils and gcc for /tools.
Depends on how long the procedures are. If you look at some packages,
say qemu or qt, they get pretty long. There could easily be a
lexlive-pass1 and texlive-pass2 on the same page and, depending on the
content, would be my preference.
By putting it on a separate page, I could then move the PATH setup
so that both the binary and the pass-1 versions lead to that.
But, I sort of expect that changing it like this might upset
somebody. If so, please speak up now ;-)
There is no problem with setting it up one way, evaluating, and making
changes. It helps to have an initial version to do constructive critiques.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
