Outline of phases

Home | Packages | Files | Procedures | Keywords | External packages

Well, I modelled the operation of ::makedist::do closely along the steps I took during manual operation. That being:

1. Retrieve the module, into a separate playground (the build directory). This might be a special (tagged) version.
2. Go into the module directory and tweak it as desired, add version information here, insert a date there, remove this file, etc. Alas, prepare it for distribution.
3. Step out of the module, copy some descriptive files, like README to another location, generate the archive(s) to be distributed. We do pack it.
4. Transport archive and saved files to their final destination.

For all but the 2nd phase the general code just makes a lookup of the internal name specified for that phase and calls the associated externally defined procedure. Their definitions reside in the directory lib/plug and are read automatically at the first use of a command defined in lib/engine.tcl.

These external procedures are called

1. retriever,
2. packer,
3. and transport respectively

They have to adhere to well defined interfaces to enable them being easily plugged into the framework provided here.

Next

Generated by AutoDoc 2.1 at 06/05/1999, invoked by Andreas Kupries