|
1 year ago | |
---|---|---|
.. | ||
punk | 1 year ago | |
struct | 2 years ago | |
textutil | 1 year ago | |
README.md | 2 years ago | |
cksum-1.1.4.tm | 2 years ago | |
cmdline-1.5.2.tm | 2 years ago | |
fileutil-1.16.1.tm | 2 years ago | |
http-2.10b1.tm | 1 year ago | |
mime-1.7.0.tm | 1 year ago | |
natsort-0.1.1.5.tm | 1 year ago | |
oolib-0.1.tm | 1 year ago | |
overtype-1.5.0.tm | 1 year ago | |
punkcheck-0.1.0.tm | 1 year ago | |
textutil-0.9.tm | 1 year ago |
README.md
This is primarily for tcl .tm modules required for your bootstrapping/make/build process. It could include other files necessary for this process.
The .tm modules here may be required for your build script if it intended the installation operator uses an existing tclsh or other shell as opposed to a tclkit you may have for distribution which is more likely to include necessary libraries.
The modules here are loaded by your initialisation scripts and so can be a snapshot of different versions than those in your project src. The modules can be your own, or 3rd party such as individual items from tcllib.
You can copy modules from a running punk shell to this location using the pmix command.
e.g
pmix visible_lib_copy_to_modulefolder some::module::lib bootsupport
The pmix command will help you pick the latest version, and will create any necessary file structure matching the namespace of the package.
e.g the result might be a file such as /src/bootsupport/some/module/lib-0.1.tm
The originating library may not yet be in .tm form. You can copy a pkgIndex.tcl based library that is composed of a single .tcl file the same way using the above process and it will automatically name and file it appropriately but you need to check that the library doesn't require/load additional files - and that it is Tcl script only.
Always verify that the library is copyable in this manner and test in a shell with tcl:™️:path pointed to ./bootsupport that it works.