subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cooke, Mark" <mark.co...@siemens.com>
Subject RE: project vs. repository
Date Thu, 13 Jan 2011 07:36:42 GMT
> -----Original Message-----
> From: alan.james.taylor@gmail.com 
> [mailto:alan.james.taylor@gmail.com] On Behalf Of Alan Taylor
> Sent: 13 January 2011 00:22
> To: users@subversion.apache.org
> Subject: project vs. repository
> 
> Greetings,
> 
> Some time ago I created my repo with:
> svnadmin create /srv/svn/cfg
> 
> This has been operating fine for over a year, but I now have
> a problem because I want to add another project.
> Unfortunately I think the original repo creation command
> should have been:
> svnadmin create /srv/svn
> 
> My problem is that cfg should be a project within the repo
> and now I want to add another project, i.e.
> /srv/svn/cfg
> /srv/svn/pxe
> 
> What is the best way to move things around ?
> 
> Rgds/Alan
> 
I use svn from windows but I assume you are using some *nix flavour...

It depends on what you want to achieve.  Are the two projects related?
Some people favour keeping separate repos for separate projects (a bit
more admin to create new repos each time, my choice!) or keep everything
in one repo (more admin if when you try to archive off dead projects).

First make sure no-one is using the repo and that everything has been
checked in (not completely required but saves hassle), then shut down
however you serve your repo (apache, svnserve).

To use one repo... I would open a TortoiseSVN repo-browser window and
create a new 'cfg' folder in the repo and just move the project files
under that.  I believe that you can achieve the same from the command
line using the mv command with the appropriate two URLs.  Now you can
add a folder your second project...  You may want to move the repo up a
folder in the filesystem.

Alternatively, create your second repo just like you did the first.

The next step requires you to change the setup of how you serve your
repo (svnserve or apache will be different).  If you now have two repos
then you need to look into the ParentPath options (e.g.
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html).  If
just one repo then you might need to change the address from which the
repo is served so that /cfg is no longer a part of it (e.g. your apache
<Location> directive section)...

You will probably need to checkout new working copies from the new
locations or you could try using svn switch
(http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.switch.html)

Good luck,

~ mark c

Mime
View raw message