RE: cvs add <directory>

[Greg A. Woods]

[ On Friday, May 23, 2003 at 15:25:51 (-0700), Shankar Unni wrote: ]
> Subject: RE: cvs add <directory>
>
> I know that the CVS aficionados like to think of directories as just
> artifacts of some arbitrary file arrangement, but the actual directory
> organization is important in many (most) cases. 

Indeed, but all of this "organization" is automatically and
transparently handled by CVS.  Directories exist when they need to, and
not otherwise.  Files come and they go as content is commited to them
and as they are marked dead.

> Consider, for instance, a product script setup that's checked in to CVS.
> If the product's directories are reorganized in the future such that
> files move around, it's important to be able to keep the file's history
> separate from that of its location in the tree, so that I can see a
> unified history of the file across that move. Having to "delete" the
> file from one location and "create" it another breaks the history chain.

You are very confused.  Nothing is broken or lost when files are removed
from one location and added in another.  When you rename files you
simply commit the necessary changes to the scripts which know the names
& locations of these files at the same time as you commit the adds and
removes and all is as it should be.  (i.e. always commit _only_ when
everything is working togther)

Old releases can be checked out and the files will appear in their old
locations and the old scripts will refer to them in their old locations.

New releases can be checked out and the files will appear in their new
locations and the new scripts will refer to them in their new locations.

There is no magic -- it just works that way by design.

-- 
                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>