Article:
 |
|
In Sync with CVS
|
| Subject: |
|
Subversion |
| Date: |
|
2003-07-22 04:43:05 |
| From: |
|
anonymous2
|
|
|
|
Although not officially "production" ready, I've been using Subversion to back up my system:
http://subversion.tigris.org/
It handles binary diffs and moving files, two of the biggest day-to-day problems I've had with using CVS. It also uses HTTP/WebDAV as its transfer protocol, which makes my company's sys-admin happy. The command line interface is very CVS-like, so it wasn't hard to pick up once I understood the underlying architectural differences
On the down side, it's /much/ more complex than CVS at this point, and took a while to install on my TiBook.
Here’s a good o’reillynet article from last year on subversion if you’re curious:
http://www.onlamp.com/pub/a/onlamp/2002/10/31/subversion.html
|
Showing messages 1 through 1 of 1.
-
Subversion on Macs
2005-01-31 07:24:08
mizumitai
[View]
What I did:
1) Install the Subversion 1.1.3 package from Martin Ott of SubEthaEdit fame:
http://www.codingmonkeys.de/mbo/
2) Install svnX:
http://www.lachoseinteractive.net/en/community/subversion/svnx/download/
3) Set up my ssh login: Create my user with the svn group on the server. Add the line "umask 002" to my .bash_profile. Set up password-less login with ssh-keygen by copying my public key to the authorized_keys file in ~/.ssh/ on the server.
4) Get the admin (or someone with sudo) to make the respository folder: "svnadmin create /home/svn//myRespository/"
5) Open svnX. Specify the respository string. If you're using ssh, something like "svn+ssh://username@example.com/myRepository/". Also specify the local checkout directory in the Working Copies window.
6) Check out your respository from the server. Add files and folders to your working copy. Click the Add or Update button as necessary to commit to the server.
7) Check to make sure everything was added properly by clicking Go to Repository.
And that was it...
And, at least for my test cases, Subversion seems to handle resource forks okay...