[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: where should i put the server config files

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-08-02 20:50:45 CEST

On Sun, 2004-08-01 at 03:08, robert rottermann wrote:

> I have converted some 200 projects from cvs to subversion usin cvs2svn.
> now I have some 200 svn repostories.
> Can I have a config file for them all?

Each repository has its own config file for svnserve. I suppose you
could 'share' a single file by creating symlinks....

> Or did i make a mistake creating my structure?
> What I did was :
> the old structure was:
> /home/cvshome/
> /proj1
> /proj2
> ..
> each proj I transformed with cvs2svn like follows:
> in /home/svn:
> svnadmin create --fs-type fsfs projXX
> csv2svn --existiong-svnrepos projXX /home/cvshome/projXX

It's not a mistake to create a separate repository for each project,
it's just one possible choice. The other choice was to create one big
svn repository for all the projects. Chapter 5 discusses the pros and
cons of these two options.

> what I have done is I checked out a workin directory like that:
> svn svn://salome.redcor.net/home/svn/proj1/trunk proj1

Is this a typo? There's no subcommand there. Did you mean,

   'svn checkout svn://..../trunk proj1' ?

> now I ch to proj1 and issue the command
> svn co
> however I get a help screen indicating the correct use of co
> usage: checkout URL... [PATH]

Well, sure. 'svn checkout' takes one or two arguments. But if you
already did a checkout, and the proj1 working copy was created as a
result of that, why are you trying to run 'co' a second time?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 2 20:53:09 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.