Max Bowsher wrote:
> I wrote my question after *carefully* studying the code and compat
> rules. Would you please answer it with more detail than an elaborately
> worded "RTFM".
Ad 1: Even on ELF systems, we don't encode the version number in the
SONAME. As far as the dynamic loader is concerned, it's always 0.0.0.
But even if we did, Subversion works on systems that don't use ELF
binaries; Windows being one such system, and I suspect there are others.
So the version check done by the dynamic loader is irrelevant.
We do encode the major version in the name of the library on all systems
I know of.
Ad 2: I guess you're thinking that we don't have to check "lib_minor >=
my_minor" because the program will fail to start anyway if the APIs are
missing. This isn't the case with on-demand loaded binaries; it's also
entirely reasonable for an application to require a certain version of
the libraries even if previous versions have all the APIs, e.g., if
those previous versions contain a known bug.
Ad 3: The compatibility check is stricter for development versions, with
good reason.
Many people have been bitten by mismatched library versions on their
system, and there's at least one documented case where the version
checks detected that and printed a better error message.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 7 17:04:38 2004