Processing Subsequent Baselevels

Now, you need to “layer” the files in the next baselevel on top of the files that you’ve already placed under AccuRev control.

1.	Change the definition of the import workspace:

cd D:\baselevels\gizmo2.0
accurev chws -w import -l . ( again, “dash-ell dot”)

In effect, you’ve moved the workspace to where the files are, instead of moving the files into the workspace! The files fall into several categories.

2.	Make sure that all files in this baselevel have timestamps that are later than the timestamps in the preceding baselevel:

accurev touch -R .

3.	Process the files that changed from gizmo1.0 to gizmo2.0.

To AccuRev, these files appear to be modified versions of the gizmo1.0 files that you add’ed and promote’d in the preceding section. You can list all these “modified” files:

accurev stat -m

And you can keep the new versions of the files:

accurev keep -m -c "my comment"

4.	Process the files that didn’t change from gizmo1.0 to gizmo2.0.

You don’t need to do anything about these files. In particular, you don’t need to keep new versions.

5.	Process the files that didn’t exist in gizmo1.0, but do exist in gizmo2.0.

These files are external, because AccuRev hasn’t seen them before. (Just as all the files were external when you placed the first baselevel under version control.) Add the external files to the depot, just as you did in the preceding section:

accurev add -x

As above, you may want to use stat –x and ignore patterns to filter out unwanted files before entering the add command.

6.	Promote the new files and changed files:

accurev promote -k

You’ve now placed two baselevels under AccuRev control. Layering the third baselevel, gizmo3.0, on top of the second one is exactly the same as layering the second one on top of the first. Just repeat the steps in this section.

Handling Additional Baselevel-to-Baselevel Differences

In the discussion above, we broke a baselevel’s “new layer” of files into three categories. This was a bit oversimplified — there are additional categories to consider.

•	Files that existed in one baselevel, but were deleted in the next baselevel.

You can make such files disappear from the new baselevel by defuncting them:

accurev defunct <filenames>

•	Files that were renamed from one baselevel to the next.

This will appear to be (1) a file that existed in one baselevel, but was deleted from the next baselevel, along with (2) a new file that didn’t exist in the preceding baselevel. If you know that file oldname.c in the preceding baselevel was renamed to newname.c in the next baselevel, use this series of commands to make the connection:

accurev pop oldname.c
ren newname.c SAVEME (UNIX/Linux: use the mv command)
accurev move oldname.c newname.c
ren SAVEME newname.c
accurev keep newname.c

Now, AccuRev knows that the element formerly known as oldname.c is henceforth to be known as newname.c (until the next name change, that is!).