Re: svn commit: r1379474 - in /subversion/trunk/subversion: include/private/svn_sqlite.h libsvn_subr/opt.c libsvn_subr/sqlite.c libsvn_subr/sysinfo.c libsvn_subr/sysinfo.h

[Daniel Shahaf <d....@daniel.shahaf.name>]

Branko Čibej wrote on Fri, Aug 31, 2012 at 16:59:57 +0200:
> On 31.08.2012 16:57, brane@apache.org wrote:
> > Author: brane
> > Date: Fri Aug 31 14:57:07 2012
> > New Revision: 1379474
> >
> > URL: http://svn.apache.org/viewvc?rev=1379474&view=rev
> > Log:
> > With "svn --version --verbose", print compile-time and run-time versions
> > of APR, APR-Util and SQLite.
> 
> This change takes care of the hard dependencies that are always linked
> with (or compiled into) libsvn_subr. I'm not sure what to do with serf,
> BDB, etc. that libsvn_subr does not depend on. I feel it would be wrong
> if we linked them in, but can't think of another way to find the
> run-time versions of those libraries.

Makes sense.  How about teaching the higher-level libraries that do link
those external libraries (eg: libsvn_fs_base) to report the version
numbers of the dependencies?

I'm not sure how to get the output all the way to the client, though.
For RA providers and FS providers, the providers support a "my version
string" API and there is a way to enumerate the available providers,
thus yielding output such as:

[[[
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme
]]]

But I'm not sure that this approach generalises to all optional external
dependencies we have.  (Case in point: libsasl as a subsidiary of
libsvn_ra_svn.)

> 
> -- Brane
> 
> -- 
> Certified & Supported Apache Subversion Downloads:
> http://www.wandisco.com/subversion/download
>