[NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Hans Hagen]

On 3/26/2023 3:08 PM, Carlos via ntg-context wrote:
> On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context wrote:
>> Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
>>
>>>>> fonts           | names | 3092 afm files checked,   okay
>>>>> fonts           | names | identifying tree font files with suffix 'AFM'
>>>>> fonts           | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files
>>
>>>>> fonts           | names | variable 'OSFONTDIR' specifies path '/home/ce'
>>>>> fonts           | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts'
>>>>> fonts           | names | globbing path '/home/ce/**.otf'
>>
>> There is something strange here.
>> Is maybe TEXMFHOME set?
>>
>> Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf
>> might interfere.
>> Look into /usr/local/texlive/2023/
> 
> I'll check again to make sure. But keep in mind this issue predates the official TeX Live installation . I've been using the distro prepackaged for a while. And yes. It's always been there. Sort of like, it came with the system :)
>>
>> Since it scans everything in your home directory, maybe TEXMFHOME or
>> OSFONTDIR is set to ~ (instead ~/texmf) there?
> 
> But even if there was a conflict, it wouldn't justify to be scanninp up everything viciously.

Well, if fonts can be anywhere that means checking for them anywhere. 
TeX installations have some directory setup for a reason. Imagine that 
you set up the installation to include that wildcard path in TEXINPUITS 
then every run that whole tree would get scanned for a file you ask for 
and that is not in the current directory. The whole idea behind TDS and 
defining paths for specific kind of files it to limit lookups.

> So far I've had to move about 7-8 folders. About 6 of them are owned by root, the rest are owned by root but symlinked to user.

I would not do that, instead I'd fix ny OSFONTDIR path. Even with some 
directories moved you still end with plenty useless scanning.

> And to top it off, after doing so, it didn't stop there, heck no, it also wanted to snoop in a folder with cache and headers.
> 
> To be honest. I woudlnt' know what to make of it. If it's simply looking into the permissions of the directories first,  or the fact that it has a colon separated pattern. But. Then again. The other folders didn't have it.
> 
> I'll let you know.
What if you use the regular context installation (not texlive) and see 
what that does? Maybe that gives a clue.

(btw, the official texlive 2023 was tested on windows, linux and osx so 
there must be something special at your end.)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------