> The main complication is dealing with SCCS keywords, which we want to
> check in unexpanded. One option would be to do a mass "sccs edit"
> prior to copying the source tree. Another option would be to copy the
> files one at a time, using "sccs get -k -p $file > $newpath/$file".
I wouldn't do "sccs edit." It modifies the state of the source
workspace, and it'd be nice to avoid doing that. (The source might
even be on a read-only mount point.) "sccs get -skp $file" is much
better.
You should also check for editted files in the source workspace.
Looking for "SCCS/p.$file" should be sufficient. If there is one,
then you could do one of two things:
1. Bail out; it's an error.
2. Do the "hg add ; hg commit" using the version of the file you get
from "sccs get -skp", and then, after the commit is done, copy
over the editted file to the new hg workspace.
Doing (2) preserves the state of editted files.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
