TeX Live support for custom binaries

It is possible to install and use TeX Live with binaries that are not part of the original distribution. The most common case for this is when you are on a platform which the original TL distribution does not support.

Using a custom binary set

Given a set of binaries, here are the steps to use it:

  1. Acquire the “foreign” binaries and put them (unpacked) in, say, /tmp/foobin:
    mkdir /tmp/foobin && cd /tmp/foobin
    tar xf ...tar.gz
  2. Run install-tl --custom-bin=/tmp/foobin.
  3. Add TLROOT/bin/custom to PATH. The “/custom” there is literal, and TLROOT is wherever you installed TeX Live, /usr/local/texlive/20yy by default.

Updating custom binaries after installation

Regarding subsequent TL package updates from the net: ensure that you have wget, xz, and xzdec available in your PATH; otherwise, TL will have no way to download or decompress packages.

Also, there will be no updates to the platform-specific packages in TL, since the custom platform doesn't exist in the canonical TL repository. Therefore, you will have to manually adjust symlinks in your custom dir if you want them to stay updated.

For example, if a new package is released with a new script that is added as a symlink to TL's own bin/ directories, you will have to add the symlink yourself to your custom bin directory. Likewise for deletions and changes.

Robert Alessi's OpenBSD support provides command for updating script symlinks (tlobsd mksymlinks).

Using a second custom binary set

If you want to install a second set of custom binaries (from, say, /tmp/barbin), you first have to manually rename the first set, like this:

  1. mv TLROOT/bin/custom TLROOT/bin/custom-foo
  2. mkdir TLROOT/bin/custom
  3. cp /tmp/barbin/* TLROOT/bin/custom
  4. Switch your PATH between TLROOT/bin/custom and custom-foo to control which set is current.

$Date: 2025/01/24 18:09:40 $; TeX Live; TUG home page; join TUG/renew membership; webmaster; facebook; x; bluesky; mastodon.