[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: robert rottermann <robert_at_redcor.ch>
Date: 2004-08-01 10:08:42 CEST

Thank you for your answer

Ben Collins-Sussman wrote:
> On Sat, 2004-07-31 at 15:08, robert rottermann wrote:
>
>>Hi everybody,
>>
>>I just installed subversion 1.1rc1.
>>
>>Now I wonder where i should place the cconfig files for svnserver?
>
>
> After creating a repository, in repos/conf/, there should already be a
> sample 'svnserve.conf' file for you to edit.

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?

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

>
>>And as on old cvs user:
>>Is there a way to execute a svn command in the "sandbox" without
>>mentioning the repository?
>
>
> Of course. Almost all subversion commands operate within a working copy
> ("sandbox"), and most of them don't mention the repository URL at all.
>
> If you want a more specific answer than that, ask a more specific
> question. :-)
>
sorry for beeing thick

what I have done is I checked out a workin directory like that:
svn svn://salome.redcor.net/home/svn/proj1/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]

thanks again

Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 1 10:09:06 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.