[ale] OT: move CVS module

[Michael Hirsch]

On 9/28/05, lyric hartley <leeslist at gmail.com> wrote:
>
> I have a project that has a directory in side of it that has become a
> project of its own...I would like to change it to a top level project
> without loosing its history...a few options i have considered
> - abandon the whole project starting with the two new ones...history
> is in the old one if needed
> - move the whole project to a new repo. and not use but have as a
> reference...remove it in the repo i use and import the stuff i need
> into a new project
> - move it and use a script to update the files with the new info (scary!)


A lot depends on how stand-alone it is.

To move a directory in CVS, the approach that works best for me is
1. get root on the server, or at least log into the server with a userid
which allows you to directly modify the files in the CVS repository.
2. Make a backup of your repository.
3. copy the directory inside the repository to where you want it to be. Use
"cp -a" or you'll have to go back and change the ownership and permissions
of the resulting new directory. If you have to create directories in the
repository, make sure you change the owners to something appropriate for
your repository.
4. Log into your client machine as a regular user and see that you can check
out the files in the new repository.
5. Tag the files in the old repository so you can roll back the next step if
desired.
6. Once you are convince you can work with the new repository, use standard
CVS command to remove the files from the original repository.

This procedure works very well. It lets you move the files and still keep
the history of each file. The reason you don't just move the files on the
repository is that would screw up every user's checked out files. They
wouldn't get the delete message and so their files will stick around. Then
they'd chek them in and you would have files in two places. Oh, the
headaches!

Michael
-------------- next part --------------
An HTML attachment was scrubbed...