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

Re: [PATCH] Dehardcode the Python bindings version in the installer generator

From: Roman Donchenko <DXDragon_at_yandex.ru>
Date: Fri, 31 Jul 2009 19:21:43 +0400

D.J. Heap <djheap_at_gmail.com> писал в своём письме Fri, 31 Jul 2009
18:49:32 +0400:

> On Fri, Jul 31, 2009 at 8:32 AM, Roman Donchenko<DXDragon_at_yandex.ru>
> wrote:
> [snip[
>> Sure I did. Committed in r38511.
> This builds the installer, it doesn't install the bindings and no step
> in our build process installs the bindings that I know of, so how does
> this work? Am I missing something or is it just pulling in the last
> installed bindings version?

When we run the script, the bindings we are packaging should be in the
current directory, and thus can be imported used from within the script.
Since the version of the bindings is equal to the version of Subversion
they are built against (which is recorded in SVN_VER*), we can just
substitute the latter.


Received on 2009-07-31 17:22:07 CEST

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