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

Re: [Issue 1125] - Python SWIG bindings don't install correctly

From: Brandon Ehle <azverkan_at_yahoo.com>
Date: 2003-02-07 00:07:00 CET

>If $prefix/lib/pythonXXX/site-packages/ exist, then we'll install
>there. If it does not exist, then we'll install in $prefix/lib/svn-python/
>The basic story is that if the prefix matches the python installation,
>then we'll be set. If it doesn't match, then we shouldn't try to
>create the area, nor should we go outside of $prefix to install bindings.
>The .../site-packages/ thing can also be overriden by Python itself,
>which just means that we do the comparison to ensure that what Python
>says resides within our prefix.
>The path should also be overridable by a configure switch. e.g.
>--pythondir=FOO. If that happens, then all prefix testing is ignored
>and we just install in that location.
>(all IMO, and most of this logic is not present; the newer swig
>building in Makefile.in does do the lib/svn-python/ thing tho)
I'm pretty clear on what you're trying to say, but there is one question
left unaswered.

I install a stock Linux distro, my python sits in /usr and doesn't
recognize any modules in /usr/local/pythonXXX/site-packages.

In the subversion dir, I run the following:

./autogen.sh && ./configure && make install && make install-swig-py-ext

At this point would gsvn work?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 7 00:06:35 2003

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