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

Re: Version compatibility of mod_*_svn to libsvn_*

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-10-11 15:38:48 CEST

Greg Hudson wrote:
> But people definitely upgrade from maintenance releases to later
> releases, and if they're allowed to mix and match Subversion libraries,
> then they'll run afoul of the compatibility policy as understood by Max.
> (Unless we also add the double-underscore symbols on the trunk and
> maintain them as if they were part of the public API. We've done that
> belatedly in one instance, because people *do* sometimes use mismatched
> versions of mod_dav_svn due to vendor packaging issues, and a
> maintenance release caused mod_dav_svn to be using double-underscore
> symbols.)

We need to make a distinction between the Libraries and the Apache Modules. It
seems that we can't lump both into a monolithic installation, required to stay
as a matched set, if the modules are being distributed separately. In that
case, we need to state clearly that the modules are clients of the Subversion
Libraries, and so must follow compatibility rules. Yes?

(I don't think there's any doubt that the Libraries should be required to stay
as a matched set.)

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 11 15:39:41 2005

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

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