Re: Setting up Subversion (was: Setting up CVS so it actually works!)
Re: Setting up Subversion (was: Setting up CVS so it actually works!)
- Subject: Re: Setting up Subversion (was: Setting up CVS so it actually works!)
- From: Terrence Talbot <email@hidden>
- Date: Sat, 10 Jul 2004 14:25:14 -0700
On Jul 10, 2004, at 1:16 PM, Nick Zitzmann wrote:
On Jul 10, 2004, at 1:14 PM, Jeff Ganyard wrote:
My problem is that I do need a multiuser/network solution with ssh.
And from what I've read/tried that means Apache2 with WebDAV and
that's were I had I problems last time I tried.
Not quite; Apache doesn't do SSH. Apache does SSL, which is different
from SSH. If you want SVN+SSH, all you need to do is have svnserve
installed, run OpenSSH's server on the server computer, and make sure
the user has at least read permission on the repository & database.
Then you can do something like "svn co
svn+ssh://somehost.com/path/to/repository" to do a checkout.
Yes, I use svn+ssh with no problems. Avoids having to deal with Apache2
and WebDAV installation/configuration and works more or less exactly
like cvs ext: with ssh did.
One thing that was hard for me to figure out, and doesn't seem to be
covered well in the book, is setting up something like a
CVSROOT/cvsignore file so that imports don't suck things in that you'd
rather not see in the repository.
My ultimate solution was to create an /etc/subversion directory on the
server that contains the repository and put a config file in there with
a global-ignores line that includes the usual suspects, e.g.,
.DS_Store, build, *~.nib, etc.
The easiest way to do this is to set up a quick local (test)
repository, add something, and then check it back out. Using the svn
client locally will create a ~/.subversion directory with the standard
files in it. Copy that to /etc/subversion on the server, edit config
appropriately, and then import/add/whatever.
If you set global-ignores on both the server and your home directory,
new files matching those patterns will be effectively ignored during
imports, updates, etc.
Also, I've begun using config's auto-props section for attaching
keywords and things to specific file types (like *.m) so that each new
file added to the repository doesn't have to have its props twiddled on
the command-line.
If anyone thinks what I've done isn't a good idea, let me know. :-)
Otherwise, I hope this helps. (I've also gotten ViewCVS talking
correctly with Subversion if that's of interest to anyone.) I'm less
than a week into it, but already Subversion seems a *vast* improvement
to CVS.
Cheers!
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.