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

Re: [PATCH] Have svn require Neon 0.19.3

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-02-26 04:24:58 CET

On Mon, Feb 25, 2002 at 10:05:27PM -0500, Ben Collins wrote:
> On Mon, Feb 25, 2002 at 06:36:31PM -0800, Greg Stein wrote:
>...
> > We would need all three: major, minor, and patch. API changes occur even
> > between patches, so we will sometimes need to specify a specific patch
> > release.
>
> That's pretty flawed, IMO.

Eh? The API isn't stable, and it changes between patch levels. Neon has not
seen a 1.0 release, and its API is explicitly subject to change.

Personally, I'm glad for it. I will *happily* update our use of Neon, if
that change to Neon improved it. I would hate to see a case where Neon (or
any other Open Source package) got held back from doing the Right Thing.

>...
> I was thinking something like:
>
> NEON_VER_REGEX="'0.19.[2-9]'"
>
> NEON_VER=`neon-config #or whatever`
>
> NEON_PASSED=`echo $NEON_VER | grep -E $NEON_VER_REGEX`
>
> if test "$NEON_VER" == "$NEON_PASSED"; then
> # Kick ass, this version is ok
> fi

Sure, as long as we stick to a lower/upper bound concept. The mechanics
don't bother me.

Patches welcome :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:09 2006

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.