Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of qazwart@gmail.com designates
 74.125.82.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=rEnzyMMHwhFJQrVxa30v3XzqtWWfiVVturNH/QoRzqNiz8j+xWtDjYA3GVJPJaP/dC
         6HtrsQH6OedAsAZ73X5u8nYZmI9vs0bsa2MDEXgQf9gT56dYFev9afcxBKI8kr5q2i2U
         SkqC2FSgeW/lK8sTU3X70c08Zqi9QPEnWHWls=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=6vB1UWFF5-t2sa2oznM5N7anf7RfBqnDCpjSn@mail.gmail.com>
References: <AANLkTi=6vB1UWFF5-t2sa2oznM5N7anf7RfBqnDCpjSn@mail.gmail.com>
Date: Thu, 13 Jan 2011 11:19:54 -0500
Message-ID: <AANLkTi=S9Zq4p2FQ0gSKkQb0PLPkEoCsmARLp=_Shd43@mail.gmail.com>
Subject: Re: project vs. repository
From: David Weintraub <qazwart@gmail.com>
To: Alan Taylor <ataylor@ieee.org>
Cc: users@subversion.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Are you using file:// URLs? You should either be using svnserve or
Apache httpd as your Subversion server. Fortunately, you can easily do
that without having to do anything with your repository. Even when I
have a personal Subversion repository and I'm the only user, I still
use svnserve.

But getting back to the issue at hand: Your basic issue is that your
repository root is the project itself, and not a directory holding the
various projects. There are several ways you can handle this:

* One is a dump and reload which puts your "cfg" project under another
directory. It's simple enough to do. If you do this, all of your "cfg"
project will appear as if you've always had it setup that way. (See
http://bit.ly/fdJjX5).

* Another thing you can do is simply create another root level
directory, and then copy  your cfg project under that directory. This
is easier since you don't have to shut down your repository or do a
dump and filter. However, users should be warned in advanced that this
is taking place since it changes the URL from where  they have checked
out their code. They'll need to take this in account when they commit
their changes. Also, it can cause issues with merging since the base
URL has changed.

* Lastly, you can simply create multiple repositories with one for
each project. This has advantages and disadvantages. However, if
you're using svnserve, you'll have to use a different port for each
project. If you use Apache httpd, there's no problem running multiple
repositories on the same server.

Have you seen the Subversion on line manual at svnbook.com? It's one
of the best open source manuals I've seen and does a great job
explaining not just the fundamentals of Subversion, but many of the
ins and outs of Subversion administration.

On Wed, Jan 12, 2011 at 7:22 PM, Alan Taylor <ataylor@ieee.org> wrote:
> 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
>


-- 
David Weintraub
qazwart@gmail.com