I'm sure this must have been addressed somewhere, but I can't find it...
I'm working with CVS v1.10 (Halibut). The documentation describes a
procedure for importing 3rd party source code into CVS and controlling it
there. The basic step is to do a 'cvs import' on the new sources for each
iteration of sources gotten from the 3rd party source. The one issue that I
have and don't see described is how to handle changes to the directory
structure.
For instance, assume a 3rd party product consisting of a single directory of
source code. In release 1 of the product, the directory contains two source
files (x.c and y.c). In release 2 of the product, the developer has removed
y.c and added z.c. If you simply "cvs import" release 2 of the product on
top of release 1, you will wind up with a directory that has three source
files (x.c, y.c, and z.c).
Is there a better way or a better tool for handling this? Do I have to
write a script to take care of the changes?
--
David Masterson
* KLA-Tencor Corp.
* [EMAIL PROTECTED]
