# $Id: README,v 4.2 2010/11/19 17:01:54 ksb Exp $

This is largely local policy.  We use RCS to keep our source code and have
some "standards" thay say you can't leave locked files in the master source
tree, and can't leave junk in the directories.

Your local policy might be different, but seeing how we've codified ours
might help you set you own into code.  Might even help you figure out what
you should be doing, even if it is not what we do.  For example you might
use "git" or "svk" -- they have best practices to follow, I'm sure.

If "msync" carps about a directory we try to fix it, unlock files, add files
to $SOURCE, remove junk files from the RCS subdirectory, or the like.  The
two other programs we use in this chain are "tickle" to look for stale locks
and "rcsvg" to checkout a known good copy of a source directory with locks
in-play.

This is also used from the package level to check the consistency of each
included product.  The `msync' recipe, in that case, filters the recipe
file for rcsvg commands to produce msync commands for each directory.

See the HTML index in msrc/Pkgs/Example/.

--
ksb, Nov 2010