Re: Should ".xccheckout" files be checked into source control?
Re: Should ".xccheckout" files be checked into source control?
- Subject: Re: Should ".xccheckout" files be checked into source control?
- From: Sean McBride <email@hidden>
- Date: Mon, 23 Sep 2013 11:49:16 -0400
- Organization: Rogue Research Inc.
On Wed, 18 Sep 2013 14:25:37 -0700, Jens Alfke said:
>Xcode 5 creates new files inside the project package, with paths like
> Foo.xcodeproj/project.xcworkspace/xcshareddata/Foo.xccheckout
>They’re XML plists and seem to contain info about the repository and
>submodules (at least in the case of Git).
>
>I cannot figure out if these should be checked into version control or not.
>
>Reasons for:
>* Xcode’s own commit sheet shows them in the list of files to commit, if
>they’ve changed
>* They’re explicitly in “xcshareddata” not in “xcuserdata”
>
>Reasons against:
>* They only seem to contain information _about_ the repository, which
>Xcode can glean by asking the version-control tool; not any new information.
>* I’ve seen them contain user-specific data like absolute filesystem paths.
>
>Any idea? Or can anyone describe what purpose they might serve?
I asked this on the devforum when XC5 first came into beta. Someone answered "Check out the video "Understanding Source Control in Xcode" from Friday, specifically at about 15:00. It explains this folder, basically contains info for 3rd party libraries that your project needs.".
I've added it to my svn global-ignores.
Cheers,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden