On Sep 4, 2006, at 18:11, Tom Allison wrote:
> I'm trying to configure my svn repository but it seems I am
> completely unable to create any additional projects without going
> in directly and manually creating the directories necessary to get
> the project underway.
>
> I've followed as many examples and such as I can find and they all
> end up in approximately the same spot:
>
> svn import . svn://localhost/
> svn: No repository found in 'svn://localhost'
>
> svn import . svn://localhost/testpile
> svn: No repository found in 'svn://localhost/testpile'
>
> however:
> svn checkout svn://localhost/depot/
> works like a charm everytime... So there is something there.
Subversion has no notion of a "project." There are just Subversion
repositories, which contain files and directories. You can elect to
either create a separate repository for each project, which you then
have to do manually with "svnadmin create <repo>", or you can store
all projects in a single repository, in which case then you can just
import into it which will create a new directory in the repository
for your new project. There are arguments for and against both
strategies; you'll have to decide which you want to use. It's not
super-easy, but also not impossible, to change from single-repo to
multi-repo, or vice-versa, later.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 4 19:06:00 2006