Problems with SVN.
Daniel T.
terminal window, it says 1.6.2) but when I try to do anything with svn
from within XCode, it says my client version is too old.
Can anybody suggest a fix?
Tom Harrington
<e9645662-cea8-44d0...@x6g2000vbg.googlegroups.com>,
"Daniel T." <dani...@earthlink.net> wrote:
Xcode's still using the copy at /usr/bin/svn, while you're getting the
newer version at /usr/local/bin or wherever at the command line. There
used to be an option to change the path Xcode used for svn somewhere in
Xcode. Probably there still is, but I can't find it in the latest
version. But that's what you'll need to change, if you can find out
where and how to change it.
--
Tom "Tom" Harrington
Independent Mac OS X developer since 2002
http://www.atomicbird.com/
Daniel T.
wrote:
> In article
> <e9645662-cea8-44d0-b9d1-3118ebe3c...@x6g2000vbg.googlegroups.com>,
> "Daniel T." <danie...@earthlink.net> wrote:
>
> > I have installed version 1.6.2 of svn (when I do "svn --version" in a
> > terminal window, it says 1.6.2) but when I try to do anything with svn
> > from within XCode, it says my client version is too old.
>
> > Can anybody suggest a fix?
>
> Xcode's still using the copy at /usr/bin/svn, while you're getting the
> newer version at /usr/local/bin or wherever at the command line. There
> used to be an option to change the path Xcode used for svn somewhere in
> Xcode. Probably there still is, but I can't find it in the latest
> version. But that's what you'll need to change, if you can find out
> where and how to change it.
But I replaced the 'svn' inside /usr/bin/svn. When I navigate to that
directory in Terminal, and type "./svn --version", it reads version
1.6.2.
Daniel T.
Update: It turns out that XCode is using the new version of svn, but
my .svn folder is out of date. once I re-checked out the directory,
things worked fine.
Chris Hanson
<t...@pcisys.no.spam.dammit.net> said:
> Xcode's still using the copy at /usr/bin/svn
No it's not. Xcode 3 is a Subversion client itself. It uses the
Subversion client libraries and not the command-line tool to interact
with work areas and repositories. Thus even installing a new
statically-linked /usr/bin/svn will not cause Xcode to use a new
version.
People on the xcode-users mailing list have created scripts to install
later releases of the Subversion libraries in such a way that Xcode
will use them. Note that this isn't supported by Apple, but people
seem to have gotten it to work. I strongly encourage reading the
caveats that have been posted to the xcode-users list before going
ahead and trying to force Xcode to use a newer version.
-- Chris