punkshell

Julian Noble 2d5beb5616 vfs kits: split punk9win.vfs into punk9wintk90b2.vfs and punk9wintk903.vfs Replace the single punk9win.vfs payload with two per-Tk-version kits: - punk9wintk90b2.vfs: content-identical copy of punk9win.vfs (same Tk 9.0b2-era bin/tcl9tk90.dll) except the main.tcl punk_main fauxlink was not carried over (kit is parked; its tclsh90b4_piperepl mapping remains commented out in mapvfs.config) - punk9wintk903.vfs: same payload with a newer Tk bin/tcl9tk90.dll (Dec 2025 build, Tk 9.0.3) and the old 9.0b2-era dll set aside as bin/tcl9tk90xxx.dll; adds lib_tcl9/apave4.4.10 (pure Tcl); drops the modules_tcl9 Thread-3.0b3 modules (Thread is static in the tclsfe runtime); now the mapping target for tclsfe-x64.exe (punk91 kit) src/runtime/mapvfs.config and src/runtime/vendorlib_vfs.toml (tcludp install targets) retargeted from punk9win.vfs to the new kit names. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com		2 weeks ago
..
AGENTS.md	AGENTS.md with DOX framework	1 month ago
Readme.md	misc scriptapps and file/folder organisation	10 months ago
mapvfs.config	vfs kits: split punk9win.vfs into punk9wintk90b2.vfs and punk9wintk903.vfs	2 weeks ago
punk1.ico	far too big a checkin. vfs folders that will need to be optimised later etc	2 years ago
tclkit.ico	far too big a checkin. vfs folders that will need to be optimised later etc	2 years ago
vendorlib_vfs.toml	vfs kits: split punk9win.vfs into punk9wintk90b2.vfs and punk9wintk903.vfs	2 weeks ago

Readme.md

Use mapvfs.config to configure building of a kit (metakit or zipfs) executable from customized .vfs folders within src/vfs

A runtime must be installed in the appropriate bin/runtime/ folder to build the executable. These can be installed by running: bin/runtime.cmd fetch or alternatively by downloading from an artifact source such as : https://www.gitea1.intx.com.au/jn/punkbin

Appropriate runtimes should be self-contained Tcl executables that are either metakit or zipfs aware, and have an attached vfs with 'info library' support files.

A plain tclsh, even if it has zipfs support, is unlikely to work unless it has the tcl_library folder (with init.tcl and others) and possibly some other required modules such as msgcat placed within the .vfs folder being used to build the executable.

A plain tclsh may commonly depend on shared libraries elsewhere on the system, and so the resulting executable may not be as portable.