Welcome to config-manager.
Config-manager is a tree-assembly tool. It's goal is to prepare, and aid in updating a file system tree. Currently it has support for: arch, cvs, http and ftp directory sources.
What is a config?
A config is a recipe that describes a directory tree. Typically the tree will be one ready for building software from, although other uses such as websites are possible. For example, to build GnomoVision 1.0, the author might give you a recipe that references specific exact patch version from their revision control system. They may also give you a recipe that builds GnomoVision 1.0-latest, that references a branch in their revision control system, and will build the latest released version.
Why would I want a tree recipe? Why not just issue all the RCS commands directly?
There are several reasons:
1) As a memory aid. Rather than remembering where the repository is, what tag or branch you need, and what RCS system to use, you could simply go to your config-recipes folder, pick the recipe matching what you want to get, and invoke config-manager.
2) Simplicity. recipes allow you to combine various separate sources into a single tree. So for instance, if GnomoVision requires libVision to build, you can have the source for libVision automatically retrieved (and a known-compatible version at that!) and placed into the appropriate location (be it parallel to, or nested in the GnomoVision source tree. Also, config-manager handles multiple different source types, so you only need to change your config if you switch RCS system for some elements of the config (i.e. switching from using an upstream tarball to using upstream CVS, or upstream CVS to upstream arch).
3) Repeatability. When you have a known good combination of sources at specific revisions (say your package and a couple of pre-requisite libraries), being able to reproduce that at will is useful.
Bug reports are welcome: firstname.lastname@example.org
The HOWTO and sample-config.txt are good places to read up next.