[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Library issues with multiple subversion installs

From: Micah Cowan <micah_at_cowan.name>
Date: 2007-07-04 00:04:57 CEST


Alongside the default system install of an older Subversion (1.3.1), I
have installed 1.4.4 into /opt/subversion. My trouble is that I did not
opt to install all of the same libraries (ra_dav, for instance).

When I run subversion, it checks for libraries, such as libsvn_ra_dav.
As it should, it first checks /opt/subversion. However, after that
point, it checks other system library directories. It manages to find
the old one in /usr/lib. However, this one, of course, corresponds to
1.3.1, so svn dies with "Mismatched RA version for 'dav': found 1.4.4,
expected 1.3.1" (is that message even correct? It seems to me it should
be the reverse, but maybe I'm misunderstanding the meaning. Yes, I made
sure I was running the right svn binary; specified the full path).

It seems to me that svn should handle such situations gracefully, with a
warning rather than an error, and refuse to actually use libraries whose
versions don't match expectations, but continue on otherwise. Ideally,
the warning should be suppressible.

The workaround I'm currently employing is to simply move the old ones
out of the way. This isn't a great general solution, though: what if I
had wanted to use the two different versions for different
purposes--say, one for testing and another for production use. The user
shouldn't be forced to ensure that all libraries present in the older
version are also present in the new. And what about the case where a
library name has been deprecated in the new version?


Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 4 00:05:15 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.