Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Moving projects

32 views
Skip to first unread message

Dave Sherohman

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to
I'm managing my first (substantial) repository and have just realized that,
given the number of projects in it, it would be good to create a doc
meta-project and make all the various project-specific documentation projects
subprojects of it. (i.e., instead of /proj and /projdoc, have /proj and
/doc/projdoc)

If I just rearrange the directories in the repository without telling CVS,
will it get upset? If so, what's the cleanest way to do this?

--
The Shortest Windows Manual: "Turn off the power switch."
Geek Code 3.1: GCS d- s+: a- C++ UL++$ P+>+++ L++>++++ E- W--(++) N+ o+ !K
w---$ O M- !V PS+ PE Y+ PGP t 5++ X+ R++ tv- b++ DI++++ D G e* h+ r++ y+

Donald Sharp

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to
Yes you can do this. The only caveat is that peoples checked
out trees will get confused on the next update or commit. It's best
for this sort of thing to force everyone to start over with a new
checkout of the source tree, or your gonna have to go around and hack
everyones CVS/* directory structure in the checked out tree.

donadl

Stephen Rasku

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to

>Date: Thu, 27 Apr 2000 11:26:31 -0500
>From: Dave Sherohman <da...@iggy.bridgephone.net>
>To: info...@gnu.org
>Subject: Moving projects
>User-Agent: Mutt/1.0.1i
>X-Mailing-List: <info...@gnu.org> archive/latest/16835

>
>I'm managing my first (substantial) repository and have just realized
that,
>given the number of projects in it, it would be good to create a doc
>meta-project and make all the various project-specific documentation
projects
>subprojects of it. (i.e., instead of /proj and /projdoc, have /proj and
>/doc/projdoc)
>
>If I just rearrange the directories in the repository without telling
CVS,
>will it get upset? If so, what's the cleanest way to do this?
>

CVS won't get upset but your developers might. If a developer has a
module checked out that you move they will not be able to check it in.
You can recover from this by editing the CVS/Repository file in every
module but this can be error prone.

I recommend that you make a copy of the repository which you can
re-arrange to your hearts content. I would write a script to do this so
that it is reproducable. Once it is arranged how you want it, get
everyone to release their workspaces and you can re-arrange the repository
and then have everyone check everything out again.

--
Stephen Rasku E-mail: ste...@tgivan.com
Senior Software Engineer Phone: (604) 872-6676
TGI Technologies Web: http://www.tgivan.com/


0 new messages