SVN can handle all sorts of files. Document bundles can present a challenge, but you won't have to deal with those in Xcode projects. Yes, commit all your source file (.h, .m, etc.), plist files, images, frameworks, etc. You also want to commit the .xcodeproj bundle directory, BUT you only want to commit the "project.pbxproj" file inside — any other file is specific to a given user and should not be versioned. You can exclude them manually, but the arguably better way is to modify the Subversion config file that affects all SVN clients on your machine, both GUI and command-line. That file is: ~/.subversion/config (in a hidden directory in your home folder). I suggest modifying the line that starts with "global-ignores" to look like this:

global-ignores = *.o *.lo *.la .*~ *~ ._* .DS_Store .Trash* *.pbxuser *.mode* *.perspective*

Excluding files like [myusername].pbxuser will usually drastically reduce the diffs you see. Good luck!

 - Quinn


On Sep 16, 2009, at 7:36 PM, Frank_n_Beans wrote:


I have only been coding for a little over a year now.  Versions is my
first experience with version control (LOVE THE INTERFACE). I read
somewhere that svn works best with text files but can be used for any
type of file. What is the best practice for managing Cocoa projects?
Should I upload the entire file; including .plist, .h, .xcodeproj
etc...?  I ask this because when I made a change and compared the
diff's the results were a bit overwhelming.

Thanks!
-FnB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Versions" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to