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

Re: [RFC] [PATCH] Raise minimal required version of Neon to 0.27

From: Blair Zajac <blair_at_orcaware.com>
Date: Sun, 07 Sep 2008 15:14:46 -0700

Arfrever Frehtes Taifersar Arahesis wrote:
> 2008-09-07 03:52:40 Blair Zajac napisaƂ(a):
>> Arfrever Frehtes Taifersar Arahesis wrote:
>>> I would like to suggest to raise minimal required version of Neon to 0.27.
>>> When Subversion 1.6 is released, Neon 0.26 will be very old and rather
>>> nobody will try to use Subversion 1.6 with such old versions of Neon.
>>> (r21480 removed support for Neon 0.24.)
>> I don't see the urgency in removing code
>
> OK. So what do you think about removing support only for Neon 0.25?
> Neon 0.26.0 was released about 30 months ago.
>
> r21480 removed support for Neon 0.24 about 17 months after the release of
> Neon 0.25.0.
>
>> recent bump to Python 2.4

Sorry, should have been more clear. Python 2.4 for some of our scripts and tool.

Taking a step back, I don't see why we need to update any of the dependencies
that you've supplied patches for:

1) Bash
2) Python
3) Neon

There's really nothing to gain from doing so except for limiting the systems
that svn can install on. I don't see the point. You never know when somebody
has some ancient system that they want to install svn on. It just makes it more
work then for somebody to get it installed.

I still receive the odd request to install svn on an extremely old OS and the
more dependencies, the more work.

If there's some new feature we need from a newer version of a dependency, then
sure, bump it, but otherwise, this appears to me as gratuitous upgrading.

Blair

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-08 00:15:34 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.