[tlbuild] linked scripts when script names only differ by their extensions

[Robert Alessi]

Hi Karl,

On Mon, Mar 18, 2024 at 02:45:52PM -0600, Karl Berry wrote:
> The purpose of scripts.lst is to list all the user-level scripts, i.e.,
> non-compiled executables that are distributed in Master/bin/whatever.
> 
> (I admit I don't really understand what distros do with scripts.lst, but
> I gather they do something. :)

And it is used *when and only when* TL is built, right?

> 
>     would have been to strip all the executables except the duplicates
> 
> You mean, strip as in strip(1)?
> 
>     which differ only by their extensions.  But would it have been
>     advisable?
> 
> I don't understand, but it doesn't seem like it. 

No, not as in strip(1), sorry, I didn't make myself clear.

I was simply thinking of making for OpenBSD a script that would take
the latest scripts.lst in Build/source/texk/texlive/linked_scripts/.
This script would (re)install if necessary the symlinks in bin/custom
pointing to these files "stripped" of their extensions, except for
those that only differ by their extensions, as in the case of memoize.

There may be a point in doing this, for I see that this morning
memoize r70005 was updated and I'm still left with only:

	memoize-clean -> ../../texmf-dist/scripts/memoize/memoize-clean.py
	memoize-extract -> ../../texmf-dist/scripts/memoize/memoize-extract.py

in /usr/local/texlive/2024/bin/custom

But... wouldn't that be because the update wouldn't touch what's in
custom/?  Given "custom" is not related to any supported distribution?
If so, could custom/ be included in the paths handled by the updates?

Thank you,

-- robert