Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
- Subject: Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
- From: Jeff DuMonthier <email@hidden>
- Date: Mon, 26 Nov 2007 07:54:03 -0500
On Nov 25, 2007, at 6:02 PM, David Dunham wrote:
On 25 Nov 2007, at 13:39, Jeff DuMonthier wrote:
I see it now. The project root is the folder with the project in
it (which I guess is the default). All files are contained in that
folder, but some files in the working copy are not in the project
repository because they come from other repositories.
That's the default project root, but that's not what a project root
is. From the release notes:
Xcode 3.0 has a concept of a project root, the top-level file system
directory that encompasses all your project's items (and may be at a
higher level than the project file's folder, commonly known as $
(SRCROOT)). This location is used as the base for many Xcode
features such as SCM
All project files, with the exception of system frameworks/SDK's are
in that folder so it does seem like the right choice.
On Nov 25, 2007, at 11:23 PM, Chris Hanson wrote:
On Nov 25, 2007, at 12:44 PM, Jeff DuMonthier wrote:
Which is pretty much useless unless your entire code base is a
contiguous subset of the hierarchy of one repository. I have a
separate repository for projects and project specific files, a
separate repository for common utility code and another for more
specialized modules that still may be shared among multiple projects.
Do you mix files from several separate repositories under one
directory? Subversion won't be very happy with that, regardless of
whether you use it via Xcode or the command line.
Really, Subversion expects all items within a directory to either be
part of the repository associated with the directory, or to not be
associated with any repository. I don't think the Subversion
metadata system (the .svn folders maintained by Subversion in each
controlled directory) can deal with multiple repositories claiming
the same directory.
I did not mix files from different repositories in the same directory,
however, in the project folder which is from one repository I checked
out two folders from other repositories. That configuration (which
does not mix metadata since it does not mix files, only folders) never
seemed to be a problem for command line subversion or with subversion
via XCode 1.5. I also tried setting the project root to be one level
up and moving the folders from other repositories up to that level.
Then the project root was a folder containing the project folder and
the folders from the other repositories with no mixing of
hierarchies. That caused an SCM error on opening XCode, apparently
because it expected .svn metadata at the project root level, which
there wasn't. It really does seem like the entire project hierarchy
is expected to be a subset of one repository.
_______________________________________________
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