>
>
>>What's the right solution here? Should the bindings be installed in
>>/usr/local/lib/pythonX.Y/site-packages/,
>>
>>
>
>I think installing outside --prefix is evil, unless Subversion is
>explicitly configured to do so.
>
>What happens if I have Subversion 0.18 installed and I install HEAD
>locally to experiment? If you overwrite the 0.18 Python installation
>you may break it. --prefix is the only safe place to put it.
>
>
>
>>or should Python somehow be
>>told to look in /usr/local0/lib/svn-python/ for modules to import?
>>
>>
>
>Set the PYTHONPATH environment variable?
>
>
>
The problem here as the distributers of the Python stuff, you don't have
to worry about supporting end users because they should be RTFM, but
since I am distributing applications to use the Python stuff, the users
will think its my code that is broken rather than their Python svn
extensions install. Therefore I need to support the default install of
the Python bindings whether that user has setup his PYTHONPATH or not.
Its not an issue for me, who's been using Python for several years to
know stuff like that, but it is an issue for John Doe who's never even
heard of Python, but he wants to run PySVN or whatever. I guess this
means I just need to search all the common locations that the extensions
could be installed to by default and loading the svn extensions from
there as I don't see any other way of supporting default installations.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 25 15:16:53 2003