On Mar 23, 2011, at 13:10, Luther Baker wrote: +1 for using .gitignore. You may want to include the following entries as well:build .* *.mode1v3 *.pbxuser
-Luther On Wed, Mar 23, 2011 at 2:47 PM, David Duncan <email@hidden> wrote: On Mar 23, 2011, at 12:13 PM, Quincey Morris wrote:
> I think it's even a bad idea to try and put the workspace "file" (i.e. package) under SCM control, because Xcode changes it too often. At least several times during my marathon, when I *did* have the workspace package under SCM, I couldn't push to the remote server because something part of getting to the menu item dirtied one of the private state files, so I just got told to commit first, which just took me round in a circle. But maybe that was a different problem.
We use a .gitignore file with ".DS_Store" and "xcuserdata/" entries to avoid this. Just put it at the root of your repository and you should be set.
--
David Duncan
Yeah, but -10 for this not being done by Xcode by default. We've had .DS_store files for how many years now?
If Xcode did that by default, then the future tech note lurking within David's response would just be for crazy people who actually wanted to put .DS_store etc files in their repositories -- and would say how to defeat the default. ;) On Mar 23, 2011, at 13:02, Wade Williams wrote: Couldn't you just create a local repository, and push it to the remote location via the command-line when you have an update? That's what I do.
I suspect that's the only practical answer, until Xcode 4's git SCM actually works (in less than 16 painful steps). I have hope, though, that this will addressed in an early update. It's kind of too broken to be ignored, isn't it?
The part that surprised me most was the apparent lack of integration (? compatibility? functionality?) between workspaces and git SCM. It seems like such a failure of the design imagination.
|