On 27 Jul 2008, at 16:49, J. Todd Slack wrote:
...
As for files: in general you can think of Subversion as a better
CVS. I save all sorts of files in it.
I'd echo that. Subversion is easy to set up, powerful, and you can
import all your CVS history from it (though depending on the
complexity of your branching structures, you might need to do a few
attempts). One great advantage over CVS is that you don't need to
worry about defining files as text or binary. See http://cvs2svn.tigris.org/features.html
for the conversion tool.
If you are using it for lots of other sorts of files in different
locations then I would look beyond Xcode as a client -- I've been
using SmartSVN quite reliably, though there are others (free and
commercial). I find Xcode's support useful for doing a quick diff
or log of a particular file in a project, but for any other
operations I'll do them in the client.
Currently, Xcode requires you to specify a single "project root" which
is then used for all SCM operations. This can be problematic if the
directories you care about are in different directories in a larger
SCM structure -- specifying a single directory, which encompasses all
the other directories you want, can lead to a lot of unnecessary
effort being spend on Xcode's part in getting status information for
files you don't care about. This is a known issue, and we're working
on it.
But if you can live with that restriction, the Xcode SCM
implementation in 3.0, and the refinements to it in 3.1, are quite
nice, and I recommend that you give it a try.
Any questions, send 'em to this list.
Thanks,
-- Andrew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
