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: Sun, 25 Nov 2007 15:44:11 -0500
On Nov 25, 2007, at 2:25 PM, David Dunham wrote:
On 25 Nov 2007, at 08:01, Jeff DuMonthier wrote:
The project used to be under SCM with subversion via SSH. I did
figure out how to define the repositories using SCM->Repositories
and it connects to them with no problem. Checking out files from
the repositories and doing manual updates using XCode works, but
getting it to maintain and update status is not going well. I've
read some previous messages here about project hierarchies and
repository roots having to be correct, but didn't understand what
that meant, so I'll describe what I have:
What is the project root? (You never needed to set this before.) In
the past, Xcode was happy using its anemic SCM abilities on any file
that was in the project. Now it seems to exuberantly -- but
exclusively -- offer its helpful abilities on ALL files in the
project root.
I'm not entirely sure what a project root is (unless it is the folder
containing the project, which is the root of my hierarchy) but I think
this is what I am seeing. Files that come as part of the hierarchy
with the project from the same repository (i.e. the hierarchy in the
working directory matches the repository) get handled. Files that
come from other repositories (or possible from other points in the
hierarchy from the project repository) only get handled on a per file
basis when you manually force XCode to do so. Otherwise they are
ignored for SCM.
For many of us, this is not what we want, as the root is so bushy as
to slow things down. Except that without being rooted in the root, a
file can't be SCMed.
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.
(I don't know if Apple plans on addressing this, so it's probably
worth a bug report.)
If my interpretation of this behavior is correct, I'm surprised there
isn't already screaming about it. It's actually a depreciation of
what it did before. I wanted to make sure it wasn't something simple
I was doing wrong before I filed a bug report.
David Dunham
Voice/Fax: 206 783 7404 http://www.pensee.com/dunham/
Imagination is more important than knowledge. -- Albert Einstein
_______________________________________________
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
_______________________________________________
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