Finally, I got the permission from my employer to release the
homegrown config mgmt system we use internally. From the homepage:
"Similar to autoconf, but without the auto part, CoMa provides a
uniform configuration mechanism for items. Intended to be used in
component based development (buzz, buzz) where different software
pieces are used in the context of more than one application or version
of the same application, it provides a way to configure items and
query, validate their configuration.
A special kind of item called kit acts as the descriptor for a whole
product: it can check out the needed items and configure them to work
together. At present it works best with HO-CVS, but it can get on with
pure CVS, albeit with some loss of convenience.
CoMa is written and customized in Common Lisp."
To support our development processs we needed a version control system
that can handle merges on a per branch or per commit basis, renames,
undo commits, etc. CVS fell short, SVN wasn't ready so we went with
MetaCVS. HO-CVS is basically MetaCVS plus support for module versions
and a few minor things. Module versions identify commits and are
essential for per commit merging, undoing, diffing. That said, HO-CVS
is a temporary solution and CoMa can be extended to work with other
version control systems.
CoMa is LLGPL'd, HO-CVS is of course GPL'd.
CoMa works with Clisp, CMUCL, SBCL. HO-CVS with Clisp only I'm afraid.
Since CoMa loads a lot, Clisp is the fastest (by far) of the three.
http://retes.hu/~mega/coma/
http://retes.hu/~mega/coma/user-guide.html
http://retes.hu/~mega/ho-cvs/
Gabor Melis
PS: Savages of cll, please note that some parts of CoMa were written
while being extremely new to CL. And it shows.