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

Re: Why does Subversion 1.6.x require such a recent Python?

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Tue, 19 May 2009 19:20:22 -0400

Stefan Sperling wrote:
> On Tue, May 19, 2009 at 07:38:44AM -0400, Nico Kadel-Garcia wrote:
>
>> I'm trying to get Subversion 1.6.x into RPMforge, and I've got to say,
>> the requirement for such a recent Python is fairly burdensome. From some
>> testing, it's apparently only needed for the compilation, not for the
>> actual operation of Subversion.
>>
>> I understand how that can happen: whoever wrote those bits has an
>> up-to-date development environment. But it would be helpful if we could
>> scale back that requirement a bit: it only occurred with 1.6.0, and
>> wasn't there for 1.5.6. Ws that really necessary, in revision *35307*
>> <http://svn.collab.net/viewvc/svn?view=revision&revision=35307>? Can it
>> be gracefully scaled back to only require 2.3.4, which will ease RHEL 4
>> compilation considerably?
>>
>
> Nico,
>
> can you elaborate on what problems you are facing exactly?
>
I can't compile on RHEL 4, even if I rollback the tests for python-2.4
or greater to 2.3. Arfrever's reply seems correct that

The SRPM's have a bunch of small patches, in particular to integrate
sqlite-amalgamation (which is one of the factors I'm trying to resolve).
I'd also like to have a gentle word with the smart aleck who put in the
'without_swig' settings, then removed all effect of them and simply
included the swig tarball anyway.

> this is Arfrever's reply from IRC (slightly edited to remove noise):
>
> <stsp> Arfrever, http://svn.haxx.se/users/archive-2009-05/0693.shtml
> <Arfrever> stsp: I'm not subscribed to that list...
> <stsp> Arfrever, just wanted to show the message to you in case you know
> the reason why 2.4 is required
> <stsp> I can proxy a reply for you to the list if you want
> <Arfrever> stsp: It is required to run autogen.sh or to run tests or to
> build Python bindings.
> <Arfrever> stsp: Python isn't required to build core part of Subversion
> when not regenerating build-outputs.mk.
> <stsp> why can't autogen.sh be run by earlier versions?
> <Arfrever> stsp: We use e.g. sorted() which is new in Python 2.4.
> <Arfrever> stsp: Running autogen.sh is required only after changing
> build.conf.
> <Arfrever> stsp: If somebody patches e.g. configure.ac from the tarball,
> it is sufficient to run `autoconf`.
> <stsp> ok I will send that to the list and see what the reply is
> <stsp> thanks
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2321551

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-20 01:21:30 CEST

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