Re: Setting up CVS so it actually works!
Re: Setting up CVS so it actually works!
- Subject: Re: Setting up CVS so it actually works!
- From: Heath Raftery <email@hidden>
- Date: Fri, 16 Jul 2004 18:22:25 +1000
On 16/07/2004, at 9:45 AM, Nick Zitzmann wrote:
On Jul 15, 2004, at 5:09 PM, Heath Raftery wrote:
The overwhelming response seems to echo Bill's suggestions here, so
I'm a bit lost again! I read a few of your posts Bill, on the Cocoa
mailing list and I must say, I'm no closer to a solution I'm happy
with.
I agree with Bill; I use Subversion and I'm really happy with it.
Useful to know, thankyou.
I'll offer a side discussion here then: In other IDE's I've used,
source control was a separate process to code development.
Let me guess: Visual Studio?
Borland actually. Both Builder and Delphi alongside TeamSource. Not a
great SCM tool, but generally workable.
The process was to: first visit the SCM application and update to all
the latest versions; then enter development; and then at the end of
development, kill the development app and run the SCM app again,
committing any changes. Do other people use or recommend this method
on OS X?
Yes. Back when I used CVS, I used Sen:te's CVL client as a GUI for
CVS. Now I use SCPlugin, which is AFAIK the only working GUI for
Subversion on the Mac.
Interesting. I'll keep it in mind.
And you don't have to stop Xcode, either. When you make a change to an
Xcode project, the project is immediately saved, so it's OK to run the
SCM client program at the same time as Xcode and even commit changes
to the project while Xcode is still running.
Except if you're updating. XCode might pick up the changes and new
files, but if they are open in the editor I'd expect troubles.
_______________________________________________
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.