Add support of svn 1.7

[GoogleCodeExporter]

http://grab.by/cVj4

Original issue reported on code.google.com by i100...@gmail.com on 4 Apr 2012 at 1:13

[GoogleCodeExporter]

It would be more useful if you stated which versions of svnX, OSX & Subversion 
you were using rather than providing a link to a screen shot.

Would I be right to assume that you are not using svnX 1.3.2?
<http://code.google.com/p/svnx/wiki/Changes>

Original comment by chris...@gmail.com on 4 Apr 2012 at 1:49

[GoogleCodeExporter]

If you want svnX to use Subversion 1.7.x, then you need to tell svnX where you 
installed Subversion 1.7.x.
[Via the svnX > Preferences… dialog.]

Original comment by chris...@gmail.com on 4 Apr 2012 at 1:55

[GoogleCodeExporter]

Sorry, my fault. I'm using svnx 1.3.2 and Lion 1.7.3. I was thinking that svnx 
is linked to svn library like TortoiseSVN, but it relies on command line 
client. And I have a 1.6 svn in usr/bin but from terminal I use svn 1.7 from 
MacPorts which installs to /opt/local/bin. So after I changed path to svn 
binary in settings everything started working. But maybe svnx should have it's 
own svn binary so it will work out of the box.

Original comment by i100...@gmail.com on 4 Apr 2012 at 12:46

[GoogleCodeExporter]

> But maybe svnx should have it's own svn binary so it will work out of the box.

No!  OSX already includes Subversion.  SvnX does work “out of the box”.
Why would I want to tie svnX to (& force you to use) a particular version of 
Subversion when currently it allows you to use any of over 30 versions plus any 
custom built versions?
Additionally, by svnX using your chosen Subversion CLI tools & libraries you 
are given a more consistent experience when using both svnX & the Subversion 
CLI and you can choose to upgrade (or downgrade) either independently.
So, I see no reason to give svnX its “own svn binary”.

Original comment by chris...@gmail.com on 4 Apr 2012 at 6:10

• Changed state: Invalid