Version 2 of Tcl Packaging Glossary

Updated 2018-10-22 18:58:41 by hypnotoad

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:

  1. A binary executable that can take on a VFS payload but has not yet
  2. A VFS that contains libraries of tools for a general purpose shell.
  3. A #1 that has #2 attached
  4. A VFS that acts as a single application
  5. A #1 that has #4 attached
  6. A VFS that acts as a suite of tools, which tool is decided by command line arguments
  7. A #1 that has #6 attached
  8. A Binary package that requires a pure-tcl package to be co-installed
  9. A Pure-Tcl package that exists solely to service a binary package
    1. A #8 which is bundled in a VFS
    2. A #8 which is statically linked to an executable
    3. A #9 which is installed in a VFS
    4. A #9 which is appended to the end of a dynamic library
    5. A collection of pure-tcl packages that can be broken apart (ala Tcllib)
    6. A standalone package that is within Item #14
    7. #15, installed in a VFS
    8. A C accelerated alternative to a #15 which is embedded in a DLL installed to a VFS
    9. A C accelerated alternative to a #15 which is statically linked to a #1
    10. A collection of #17s that are assembled into a dynamic library
    11. A collection of #17s that are assembled into a static library
    12. A #1 which contains a starter VFS for bootstrapping but is not the object's final form