Re: Xcode 3 SCM Preference Pane Documentation
Re: Xcode 3 SCM Preference Pane Documentation
- Subject: Re: Xcode 3 SCM Preference Pane Documentation
- From: Chris Hanson <email@hidden>
- Date: Sat, 3 Nov 2007 19:17:32 -0700
On Nov 3, 2007, at 7:04 PM, David Dunham wrote:
On 3 Nov 2007, at 17:43, Chris Hanson wrote:
Most of the questions I've seen about Subversion SCM in Xcode 3.0
appear to be either due to an attempt to assign a repository to a
project that's not in a work area, or due to an attempt to assign a
repository to a project that doesn't match the work area's
repository root.
At least two of us were wondering how to efficiently use SCM when
the true project root is full of irrelevant folders. Never saw an
answer to that one.
Right, that's the third question that's come up. I don't have an
answer for you, really, sorry. For the work I do, I use some very
large repositories, but even though a work area is a check out all of
trunk (which might pull several hundred MB), I *never* set an
individual Xcode project's project root to the top of the work area.
Instead the projects themselves are always self-contained.
I understand that your projects aren't self-contained in the same way;
in that case, I don't really know what to say. In such a situation,
whether you're using SCM from the command line or from Xcode, certain
operations are going to be relatively expensive.
One thing that Xcode *does* do, that there's currently no way to
suppress, is attempt to show you the "complete" state of all of the
files in your project. That is, not just the state that may be
different locally on disk, but also state from the repository itself.
Thus Xcode does not do the simple equivalent of "svn status" on a work
area (which will only tell you about changes local to the work area)
-- it always does the equivalent of "svn status --show-updates" which
also tells you about changes within the repository.
Whether this is a bug or a feature depends greatly on one's
perspective. I personally think it should always behave the way the
specific SCM system you're using is designed to work -- thus for
Perforce and Subversion, it would show only local changes while for
CVS it would show both local and remote changes -- but Xcode has
generally opted for consistent behavior across all SCM systems
instead. This is why it insists on showing information on both local
and remote changes for Subversion and Perforce, even though doing so
can be expensive.
-- Chris
_______________________________________________
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