> On 1 Nov 2016, at 02:57, Norbert Preining <prein...@logic.at> wrote: > > Do you *need* to recompile the binaries? > > There are options, without any problem: Debian ships TeX Live packages since > more than 10 years, > and all of them are build from source, no binaries included. It can be done, > but > it needs a bit of work. > > The easiest way if you absolutely need to compile your own binaries is as I > wrote: > * compile them > * copy them into Master/bin/$ARCH/ > * genereate a texlive.profile > * run install-tl -profile texlive.profile > > That can all be automatized and done offline and without human > attendance.
no, I don't *need* to recompile the binaries, but past experience with many other packages showed that some tools are not very happy when moved to a different folder then the one they were compiled for, so, mainly for safety reasons, I generally prefer to build everything from sources, with the actual `--prefix` set correctly during `configure`. my current solution for the extra tools required by my macOS builds is a custom instance of Homebrew, installed in $HOME/opt/homebrew; since this is a custom location, Homebrew automatically builds everything from sources; unfortunately TeX is on the Homebrew blacklist, and the only solution is to use a Homebrew Cask, which is a workaround that installs MacTex as root, in the standard location, and adds it to the PATH. although functional, I'm not at all happy with this configuration, since I would like TeX installed as non-root, in my folder, and not added to the PATH; if the existing macOS binaries work when moved to another location, I don't need to compile my own binaries. so any suggestions on how to do this will be welcomed. regards, Liviu