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

Re: svn commit: r32042 - branches/1.5.x

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Wed, 09 Jul 2008 13:06:11 -0700

> -------Original Message-------
> From: C. Michael Pilato <cmpilato_at_collab.net>
> Subject: Re: svn commit: r32042 - branches/1.5.x
> Sent: 09 Jul '08 12:53
>
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2008-07-09 17:03:51 Hyrum K. Wright napisa(a):
> >> arfrever_at_tigris.org wrote:
> >>> Author: arfrever
> >>> Date: Tue Jul  8 14:57:35 2008
> >>> New Revision: 32042
> >>>
> >>> Log:
> >>> * STATUS: Nominate r32017, r32029 and vote for r31964.
> >>>
> >>> Modified:
> >>>    branches/1.5.x/STATUS
> >>>
> >>> Modified: branches/1.5.x/STATUS
> >>> URL: http://svn.collab.net/viewvc/svn/branches/1.5.x/STATUS?pathrev=32042&r1=32041&r2=32042
> >>> ==============================================================================
> >>> --- branches/1.5.x/STATUS Tue Jul  8 14:45:29 2008 (r32041)
> >>> +++ branches/1.5.x/STATUS Tue Jul  8 14:57:35 2008 (r32042)
> >>> @@ -127,5 +126,10 @@ Candidate changes for 1.5.1:
> >>>     Votes:
> >>>       +1: dlr
> >>>  
> >>> + * r32017, r32029
> >>> +   Support Berkeley DB 4.7.
> >>> +   Votes:
> >>> +     +1: arfrever
> >>> +
> >>>  Approved changes:
> >>>  =================
> >>>
> >> Is this a bugfix or a feature?  I know that we occasionally bump
> >> accepted patch releases of our various dependencies in patch releases of
> >> our own, but I'm a little wary about this one.  I doubt many people have
> >>   an immediate need for 4.7 support, anyway.  I haven't reviewed the
> >> changes in question, though, and they may prove to be less intrusive
> >> than I think.
> >
> > Without r32017+r32029 Subversion would still build when Berkeley DB 4.7 is
> > used, but support for the Berkeley DB logging subsystem would be disabled.
> > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/upgrade.4.7/log.html
>
> In other words, we would *silently* lose support for a *very* important
> subsystem!

So users who upgraded to Berkeley DB 4.7 without this patch would have a worse Subversion experience than those who stay with 4.6? That does sound like a bug.

Could somebody with a better understanding of this issue add a note to this effect to the STATUS item. The "Justification" section sounds like it'd be a good place to put something like that.

-Hyrum

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-09 22:06:31 CEST

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.