RFC: /usr/lib/svn-python/ ---> /usr/lib/python2.?/site-packages/

Absent any objections, I'm going to try to change from installing Python
bindings into /usr/lib/svn-python/ to putting them into
/usr/lib/python2.?/site-packages/ for 1.6.x. The major motivation for
this is that the built bindings are specific to the used minor version
of Python.

As a plus point, that would mean that the bindings actually get
installed onto the default Python search path.

As a minus point, this means the overall installation prefix would be
governed by the install prefix of Python, rather than of Subversion - so
for example if Python is in /usr but Subversion is in /usr/local, the
bindings would default to going to /usr - except on a Debian/Ubuntu
system, which makes special effort to provide /usr/local extension dirs
for the /usr install of Python. But, this is the same situation we have
right now with mod_dav_svn, and presumably the Ruby/Perl bindings too?

Max.