Geek Answers Handbook

SVN and Xcode issues

I have repeatedly heard that the integration of Xcode with SVN is not enough, but seeing that I have never used it personally, I cannot help but wonder why.

Now I am starting a new project and SCM appears again. This time, though, I think I want to better understand what Xcode does and doesn't do correctly with SVN.

So, are there any horrible stories?

+4
source share
4 answers

A general non-response to what you ask for, but ...

I am a true fan of Versions (www.versionsapp.com) and it has made me not worried about any Xcode integration with SVN.

+4
source

There are no horrible stories: I've been using Xcode 3.1.2 with SVN for almost a year now, and that's good enough. Xcode SCM (version control manager) is pretty simple but stable. The only thing that fails is to delete the file.

When you delete a file, Xcode will also suggest deleting the file from version control, but when it comes time to commit it, it will complain that the file is missing. Therefore, I usually do "svn rm" from the terminal to delete the file, rather than deleting it from the Xcode Files and Groups panel. If I forget and svn continues to fuss, "svn cleanup" usually sorts it.

+1
source

This does not show progress at the time of commission or discharge. Also, if there is a conflict of project files, you are presented with options to either save it or replace it with the latest copy. In any case, some changes are lost.

In addition, SVN integration is pretty easy to use - we rely on this for several months.

0
source

Personally, the development teams I worked with never regretted switching from svn to git (sorry, Qaru won’t let me put the link) or bzr ( http://www.bazaar-vcs.org/ ). You can study them, although I know little about Xcode integration. (Everyone I know was command line junkies — or used TortiseBZR, etc. on Windows.)

0
source

More articles:


All Articles