Different svn version used than in preferences

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enter into options an alternative svn binary path (while retaining an
'svn' command)
2. Open a working copy.

What is the expected output? What do you see instead?
I expect to see my working copy.  Instead, I see an error message: svn
client too old.

What version of the product are you using? On what operating system?
Svnx 1.0 on Mac OS X 10.5.7

I suspect the reason may be that there's an 'svn' somewhere instead of a
'./svn'.

Original issue reported on code.google.com by vanc...@gmail.com on 7 Jul 2009 at 2:36

[GoogleCodeExporter]

I'm not sure what you mean by "(while retaining an 'svn' command)".

However, './svn' is NOT a valid path.
It should be something like '/usr/local/bin', '/usr/bin' or 
'/opt/subversion/bin' etc.

This is better handled & validated in svnX 1.1.

Original comment by chris...@gmail.com on 7 Jul 2009 at 4:27

• Changed state: Invalid

[GoogleCodeExporter]

Right, the option is set to '/opt/subversion/bin'.  But I have another copy of 
svn in
the unix path, which is what's getting executed.  What I meant was that if you 
go to
that directory and typed "svn" you'd be running the wrong version, which is why 
I
suspected that might be happening (as opposed to just running 
/opt/subversion/bin/svn)
Anyway, I just downloaded 1.0 so I didn't notice it was out of date.  Sorry.

Original comment by vanc...@gmail.com on 10 Jul 2009 at 5:51

[GoogleCodeExporter]

>Right, the option is set to '/opt/subversion/bin'.  But I have another copy of 
svn in
>the unix path, which is what's getting executed.

Not by svnX?  SvnX does NOT use $PATH to execute svn EVER.

>What I meant was that if you go to
>that directory and typed "svn" you'd be running the wrong version, which is 
why I
>suspected that might be happening (as opposed to just running 
/opt/subversion/bin/svn)

Are you saying that with '/opt/subversion/bin' set in svnX's prefs it is NOT 
then
using /opt/subversion/bin/svn when you open a working copy window?

However, if you are saying that typing 'svn ...' in a terminal window does not 
run
/opt/subversion/bin/svn then that's not an svnX issue.

>Anyway, I just downloaded 1.0 so I didn't notice it was out of date.  Sorry.

It's not exactly "out of date".  SvnX 1.1 is still beta, but it's still better 
than 1.0.
(And it doesn't allow invalid paths & displays the version of Subversion found.)
There's no need to apologise.
If there's a problem with svnX then I need to understand it, so I can fix it.

Is there a problem with svnX?

Original comment by chris...@gmail.com on 11 Jul 2009 at 3:20

[GoogleCodeExporter]

I am saying that with '/opt/subversion/bin' set in svnX's prefs it is NOT then
using /opt/subversion/bin/svn when I open a working copy window--it is instead 
using
another version of svn I have on the computer.

Everything else is just a guess at why.

Original comment by vanc...@gmail.com on 17 Jul 2009 at 5:44

[GoogleCodeExporter]

I don't understand how that is possible.  If the path is set to 'P' the svnX 
should run 'P/svn'.

What version (of Subversion) does svnX 1.1b3 display in the Preferences window?

What is displayed if you type `/opt/subversion/bin/svn --version` in a terminal?

Original comment by chris...@gmail.com on 17 Jul 2009 at 8:47