Assume you have a bunch of SCCS-controlled source directories in a hierachy something like
topsrc topsrc/SCCS topsrc/module1 topsrc/module1/SCCS topsrc/module2 topsrc/module2/SCCS topsrc/libs topsrc/libs/lib1 topsrc/libs/lib1/SCCS topsrc/libs/lib2 topsrc/libs/lib2/SCCSIf you 'cd' to somewhere else, like /tmp/build, and run 'sccslntree topsrc', it will make a new hierachy under /tmp/build, that looks like
/tmp/build /tmp/build/SCCS -> topsrc/SCCS /tmp/build/module1 /tmp/build/module1/SCCS -> topsrc/module1/SCCS /tmp/build/module2 /tmp/build/module2/SCCS -> topsrc/module2/SCCS /tmp/build/libs /tmp/build/libs/lib1 /tmp/build/libs/lib1/SCCS -> topsrc/libs/lib1/SCCS /tmp/build/libs/lib2 /tmp/build/libs/lib2/SCCS -> topsrc/libs/lib2/SCCSWhy bother to do all this?
Because it also does an "sccs get" for all controlled directories, which will get the latest checked-in revision of the files. You will then have a guaranteed "clean" copy of all files under SCCS control.
It lets you do this, EVEN IF DEVEOPERS HAVE FILES CHECKED OUT FOR EDIT, and will not interfere with their work in progres.
Back to Phil's Solaris pages