[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-10-10 18:50:09 CEST

On Sun, 2005-10-09 at 21:11 -0500, kfogel@collab.net wrote:
> Greg Hudson <ghudson@MIT.EDU> writes:
> > If it's so dastardly to use double-underscore symbols like this, what
> > should we do when we need to add a new libsvn_subr API to fix a bug, and
> > want to backport that bug to a previous release? In the past, we've
> > converted the new API to a double-underscore symbol. I don't think I've
> > seen you or Karl address this point so far.
> I guess I make a distinction between recommended practice and mildly
> klugey things done to get a fix into a maintenance line. People don't
> look at maintenance lines when they're doing development, generally;
> what's important is that trunk reflect The Way Things Ought To Be.

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

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 10 18:51:37 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.