You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jim Geist <ji...@lifesim.com> on 2004/11/16 19:26:06 UTC

Checking out over top of an existing directory structure

One part of our project has a bunch of data that's not in source control.
Basically there's a system, with its own directory hierarchy, that already
exists; we are making modifications to the system and want SVN to just track
our changes. Since all of our changes are in new files, I don't want to
check the whole thing in - it's about 3 gig - just our modifications.

 

If I try to do a checkout on top of the existing system's structure, SVN
complains because some of the directories in the repository already exist in
the file system. So I have to do the checkout first, then install the system
on top of the working copy. I'd prefer to do this the other way round, since
a bunch of people already have the system installed and working. I couldn't
find this in the book anywhere. Anyone know how to tell SVN that it's ok
that some of the directories already exist?

 

Thanks!

 

-- Jim


RE: Checking out over top of an existing directory structure

Posted by Jim Geist <ji...@lifesim.com>.
Thank you! This worked fine.

-----Original Message-----
From: Hiroharu Tamaru [mailto:tamaru@myn.rcast.u-tokyo.ac.jp] 
Sent: Tuesday, November 16, 2004 2:52 PM
To: users@subversion.tigris.org
Subject: Re: Checking out over top of an existing directory structure

At Tue, 16 Nov 2004 14:26:06 -0500, Jim Geist wrote:

> One part of our project has a bunch of data that's not in source control.
> Basically there's a system, with its own directory hierarchy, that already
> exists; we are making modifications to the system and want SVN to just
track
> our changes. Since all of our changes are in new files, I don't want to
> check the whole thing in - it's about 3 gig - just our modifications.

I do similar thing to just keep track of the config files of
a running system.  When I bootstrap it, I just check out a
WC somewhere, run a script that fetches any file in the
system that has the same path as one that is in the WC (IF
such thing exist), and then just copy the WC on top of the
system, together with the .svn dirs and all.

# Well, in fact, I am doing this with CVS because I set this
# scheme up 6-7 years ago, but I see no reason subversion
# should be different.

For me, it also worked around the fact that you cannot
checkout a WC as / (THE root directory of the system).

Since this bootstrapping is a very unusual event, I felt
safer that svn or cvs does not have such a knob but made me
do a brute force myself.
-- 
Hiroharu Tamaru

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Checking out over top of an existing directory structure

Posted by Hiroharu Tamaru <ta...@myn.rcast.u-tokyo.ac.jp>.
At Tue, 16 Nov 2004 14:26:06 -0500, Jim Geist wrote:

> One part of our project has a bunch of data that's not in source control.
> Basically there's a system, with its own directory hierarchy, that already
> exists; we are making modifications to the system and want SVN to just track
> our changes. Since all of our changes are in new files, I don't want to
> check the whole thing in - it's about 3 gig - just our modifications.

I do similar thing to just keep track of the config files of
a running system.  When I bootstrap it, I just check out a
WC somewhere, run a script that fetches any file in the
system that has the same path as one that is in the WC (IF
such thing exist), and then just copy the WC on top of the
system, together with the .svn dirs and all.

# Well, in fact, I am doing this with CVS because I set this
# scheme up 6-7 years ago, but I see no reason subversion
# should be different.

For me, it also worked around the fact that you cannot
checkout a WC as / (THE root directory of the system).

Since this bootstrapping is a very unusual event, I felt
safer that svn or cvs does not have such a knob but made me
do a brute force myself.
-- 
Hiroharu Tamaru

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org