Re: Subversion and XCode
Re: Subversion and XCode
- Subject: Re: Subversion and XCode
- From: Ryan Britton <email@hidden>
- Date: Fri, 25 Nov 2005 21:35:12 -0800
Not that I know of, unfortunately. I don't remember where I found
that, but I know I was having problems with interface builder
randomly killing my .svn directories. Setting that particular
setting seemed to fix it.
On Nov 25, 2005, at 9:04 PM, Will Senn wrote:
Ryan,
I just meant the main interface where you manage the project, XCode
itself, I suppose. But I think this might work anyway. I'll give it
a shot. Where the heck does one pick up this kind of knowledge
anyway, is there a list of Application properties somewhere?
Thanks,
Will
On Nov 25, 2005, at 10:45 PM, Ryan Britton wrote:
Are you referring to interface builder? Project builder has been
deprecated for some time now. If so, try this. It should
eliminate most of the svn problems you're having.
defaults write com.apple.InterfaceBuilder VersionControlDirectory
"(CVS, .svn)"
On Nov 25, 2005, at 8:02 PM, Will Senn wrote:
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
_______________________________________________
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