|
From: <apn...@ya...> - 2026-05-30 05:23:28
|
* And if there is in fact a reason this is necessary, why only for core packages?
And come to think of it, even for core packages why is the check for safe interps only necessary for zipfs builds and not for the –disable-zipfs configuration?
Most curious...
From: apnmbx-public--- via Tcl-Core <tcl...@li...>
Sent: Saturday, May 30, 2026 8:31 AM
To: 'Jan Nijtmans' <jan...@gm...>
Cc: 'Tcl Core List' <tcl...@li...>
Subject: Re: [TCLCORE] Utility of manifest.txt?
Thanks, Jan.
I don't really understand much of the rationale of the poster. For example, the statement
... a manifest file that tells the interpreter, for clear and for certain, which packages may be loaded in a normal interpreter and which packages may be loaded in a safe interpreter.
This is the first time I’ve heard of a package loading mechanism needing to check whether the interpreter is safe or not. What for? Unsafe commands would be unavailable to the package anyways in safe interpreters. And if there is in fact a reason this is necessary, why only for core packages?
(Just thinking out aloud, the question is not directed towards you!)
Not an urgent matter but just ran into it in the course of building a static BI distribution. I’ll investigate further at some point and perhaps understand the reason for its existence.
/Ashok
-----Original Message-----
From: Jan Nijtmans <jan...@gm... <mailto:jan...@gm...> >
Sent: Friday, May 29, 2026 9:10 PM
To: apn...@ya... <mailto:apn...@ya...>
Cc: Tcl Core List <tcl...@li... <mailto:tcl...@li...> >
Subject: Re: [TCLCORE] Utility of manifest.txt?
Op vr 29 mei 2026 om 17:25 schreef apnmbx-public:
>
> Any hints as to the reason for this duplication?
The complete discussion can be found here:
< <https://core.tcl-lang.org/tcl/info/4e812aadae> https://core.tcl-lang.org/tcl/info/4e812aadae>
Hope this helps,
Jan Nijtmans
|