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

[Robert Alessi]

Hi Karl,

On Tue, Mar 19, 2024 at 09:12:20AM +0100, Robert Alessi wrote:
> 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?

I think I've found where the problem lies.

In source/texk/texlive/linked_scripts/Makefile.am, I have:

   329		   echo "$$s" | grep 'listings-ext.sh\|memoize-.*\.' >/dev/null \
   330		   || target=`echo $$target | sed 's,\.[^/]*$$,,'`; \

BUT (!) in GNU grep there is no functional difference between basic
and extended grep unlike in BSD where the two are distinct.  So in
OpenBSD line 329 fails in every instance and line 330 is always
executed.

This might affect other BSDs.

This is why I am left with listings-ext, memoize-clean and
memoize-extract.

"grep -E" should solve this issue.

Besides, why \. after memoize-.* ?

Thanks,

-- robert