Apologies in advance
if this is the wrong mailing list but it's the only one that looked promising.
We have
a base set of files that we customize on a per-client basis. Each client
has a mirror image of the base directory structure. Each client does not have a
mirror image of the base files but rather only those files that require
customization exist in the client directory tree. Prior to building a client we
merge the client tree with the base tree using a simple recursive copy and then
build. That simple approach is well
organized and effective however there are some
drawbacks.
This is not the
typical branching situation since there will never be any merging of client code
back in to the main trunk. There is also
resistence to using CVS branches since everybody contributing to the project
(content developers, technical writers) must now manage branch labels versus
just plopping changes for Acme in the Acme folder. I would really be interested
in hearing from anybody who has ideas on managing highly selective
client changes for a large number of clients.
TIA
Rod