Re: Xcode 3.1.1 and Subversion 1.5
Re: Xcode 3.1.1 and Subversion 1.5
- Subject: Re: Xcode 3.1.1 and Subversion 1.5
- From: "Russell Finn" <email@hidden>
- Date: Mon, 15 Sep 2008 17:01:58 -0400
On Mon, Sep 15, 2008 at 1:34 PM, Andrew Pontious <email@hidden> wrote:
> As you expected, Xcode expects the libraries to be in /usr/lib/, because
> that's where they are in the default installation.
> ...
> It may not be working for you because you only symlinked the libraries
> starting with libsvn, whereas there are actually two other libraries (at the
> top of the list) that are needed, and which you may have old versions of.
I'm a little puzzled by all of this. When I read the release notes
stating that Xcode 3.1.1 worked with Subversion 1.5, I had expected
that this meant it would work out of the box (and was surprised when
it didn't), which implied that the Apple-supplied libraries in
/usr/lib (or possibly /Developer/usr/lib) would be updated as well.
It didn't occur to me that this meant it would work if you replaced
those libraries by hand. The conventional wisdom seems to be that
updating Apple-supplied binaries and libraries is generally a bad
idea. (At least that's what I've heard from the Python-Mac community,
for example.)
Is this replacement of the Apple-supplied Subversion libraries a
supported practice (officially or unofficially) with Xcode 3.1.1? Or
should we await an official update from Apple in a future system
software release?
(For my current projects that use Subversion 1.5 repositories, I have
resorted to using command line tools and/or external tools such as
Versions. I miss having the Xcode integration, but I can continue to
work the way I am for the present if necessary.)
-- Russell Finn
_______________________________________________
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