[tlbuild] linked scripts when script names only differ by their extensions
Karl Berry
karl at freefriends.org
Tue Mar 19 22:45:41 CET 2024
And it is used *when and only when* TL is built, right?
Unless I'm forgetting something, scripts.lst is not used by native TL at
all. We create it for the benefit of redistributors.
This script would (re)install if necessary the symlinks in bin/custom
pointing to these files "stripped" of their extensions,
I don't understand why you need a separate script. Modulo the grep stuff
we are working out, isn't this exactly what "make install" should result
in? The bin directory as you want it? (except for the special cases,
asy/biber/xindy/etc.) That is the intent.
But... wouldn't that be because the update wouldn't touch what's in
custom/?
True.
Given "custom" is not related to any supported distribution?
True.
If so, could custom/ be included in the paths handled by the updates?
Not possible, so far as I can imagine. The update has no way of knowing
what is in custom/, or any other directory that's not in the
texlive.tlpdb file.
Part of having a custom binary set is having to figure out how to do the
updates. I don't know of any general process that's been developed for
that. Sorry. -k
More information about the tlbuild
mailing list.