Hypnotoad Writes:
When dealing with Tcl packaging, our conventional terms for things get fuzzy.
Here are the cases that Hypnotoad has encountered in his travels, and needs the community to come to a consensus about what to call them:
- A binary executable that can take on a VFS payload but has not yet
- A VFS that contains libraries of tools for a general purpose shell.
- A #1 that has #2 attached
- A VFS that acts as a single application
- A #1 that has #4 attached
- A VFS that acts as a suite of tools, which tool is decided by command line arguments
- A #1 that has #6 attached
- A Binary package that requires a pure-tcl package to be co-installed
- A Pure-Tcl package that exists solely to service a binary package
- A #8 which is bundled in a VFS
- A #8 which is statically linked to an executable
- A #9 which is installed in a VFS
- A #9 which is appended to the end of a dynamic library
- A collection of pure-tcl packages that can be broken apart (ala Tcllib)
- A standalone package that is within Item #14
- #15, installed in a VFS
- A C accelerated alternative to a #15 which is embedded in a DLL installed to a VFS
- A C accelerated alternative to a #15 which is statically linked to a #1
- A collection of #17s that are assembled into a dynamic library
- A collection of #17s that are assembled into a static library
- A #1 which contains a starter VFS for bootstrapping but is not the object's final form