[cvsnt] import the same module

[zhuyunchuan]

I have do it as you say, it is right but seems to be complex.There are 
often some files in my sandbox which don't need to be put into repo, 
such as some tools or temp files. I don't think it's simple to remove 
all files which belong to the module for I had remove some useful files 
just weeks ago using 'cvs release'. Perhaps it can be done by writing a 
script.

I find there is still a problem in your method. I set a branch in the 
repo and updated my files in sanbox to the branch. Then I added new 
directories in new module and added them into the repo to the branch and 
committed. All seemed to be right. But When I recover to the old 
revision, I find that the new directory still *exist*, even there are no 
files in these directory. I hope I can recover the 'clean' tree without 
removing them manually.


Bo Berglund :
> I think that the way you do this tracking stuff is this:
> 1) Get the sources from the vendor for version 1.0 and create a tree on your disk.
> 2) Use cvs import to create the module with its branch (use a descriptive branch name)
> 3) Check out the module, update to the branch set above and set a tag on it (Ver_1-0)
> 
> Later when you get the update form the vendor:
> 1) Check out the module from cvs
> 2) Update to the *branch* so that you are positioned correctly
> 3) Unpack the new vendor sources on top of your sandbox
> 4) Many files are now colored in WinCvs
> 5) Do a cvs update. Now all files that have the same contents will revert to the normal icon
> 6) Do a cve commit on the remaining colored files
> 7) Set a tag on your sandbox (all files) with the tag name being the new version (Ver_1-1)
> 
> Problem with removed files:
> If the vendor sources turn out to have deleted a source file that was there before in the original
> import, then the steps above will not work. In that case maybe this strategy might work instead:
> 1) Check out the module from cvs
> 2) Update to the *branch* so that you are positioned correctly
> 3) Now use Windows explorer and erase all files in the module sandbox (except the CVS subdirs with the
>    control files). All files now are shown "missing"
> 4) Unpack the new vendor sources on top of your sandbox
> 5) All files are now colored in WinCvs, but there are also some that are still missing
> 6) Use cvs remove on these missing files.
> 7) Select these missing files that are now scheduled for removal (use WinCvs flat view)
> 8) Commit the changes (the removal)
> 9) Do a cvs update. Now all files that have the same contents will revert to the normal icon
>    and the removed files will be gone.
> 10) Do a cve commit on the remaining colored files
> 11) Set a tag on your sandbox (all files) with the tag name being the new version (Ver_1-1)
> 
> I don't really know if this would work but I think so. Can be worth testing.
> 
> /Bo
>