Subversion and XCode
Subversion and XCode
- Subject: Subversion and XCode
- From: Will Senn <email@hidden>
- Date: Fri, 25 Nov 2005 22:02:24 -0600
Howdy all,
Well, I've just spent a day getting svn, apache, php and such working
nicely on my Tiger box using a combination of my own knowhow plus the
guidelines from the Apple Developer Connection article, "Getting
Control with Subversion and Xcode", available at:
http://developer.apple.com/tools/subversionxcode.html
A word of advice, don't build apache with --with-mpm=worker, it
appears to cause problems with tiger, something about preforks and
knives comes to mind, but alas, that's not what this post is about.
This post concerns a much more unpleasant reality, and that's this -
it would appear that XCode's project builder deletes .svn directories
without asking, perhaps it is its prerogative, dunno, but it's pretty
annoying. I created a project, added it to source control, edited a
file here and a file there and then tried to commit the changes and
svn refused, complaining about locks and whatnot. Come to find out,
project builder treats nibs as objects and destroys and creates them
at will (wiping out subversions working files in the process).
Whereas subversion treats nibs as directories (cuz that's what they
are :) ) and stores .svn directories in them as part of it's working
directory scheme.
Just curious, what do you guys and gals think about it? Is this
something that Apple needs to fix in XCode, or something that
Subversion should handle? Personally, I have no preference who fixes
it so long as the problem goes away - I will continue to use
Subversion as I love it, but I may wind up doing archival backups in
XCode until the problem is resolve - anyone got a better idea?
Regards,
Will
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden