Well, about 6 months ago we got frustrated enough with complicated, evolving
client mappings as well as a strong desire for version-controlled client
mappings...

What Tom here created is a //clients depot that describes our users and
clients...

users own clients clients have the normal header info, plus branch-specific or global "mappings" mappings are lines of clientspecs with keywords like BRANCH and CLIENT which
later get replaced

Then, there are, of course, scripts to piece all this together and rewrite all
the client specs.

Individuals can update their //clients/clients/clientname files, but right now
only mappings can go there, so unusual stuff creates unusual mappings (for
instance, there is a 'bert.mapping' file... I wish instead that a verbatim
client-def entry existed where a snippet of clientspec could be placed into the
client file and be copied directly to the final clientspec).

I think that there is also some 'client type' stuff there, so all our normal
developers have a consistent clientspec.

We're pleased with everything this has done to manage our client specs.

Alas, though, none of this stuff is in the public depot... However, we could
consider releasing it, but our goals in doing so would be for someone to take
the concepts further rather than using it out of the box. Any volunteers?

Later, Bert

Dave Lewis wrote: