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

Re: [PATCH] swig-build-cleanup.patch

From: Brandon Ehle <azverkan_at_yahoo.com>
Date: 2002-12-11 19:48:12 CET

>On the other hand, the current Makefile.in installs the bindings into
>Subversion's install directory, which I didn't need root as. Now to
>use the system's default python in /usr/bin, it wants to install into
>/usr/lib/python2.2/site-packages/svn and I need root.
That's correct.

>Now, I have root on my systems, but I don't like to install additional
>packages into the system's python (or Perl for that matter). If I were
>to do this, I'd much rather install my own compiled python into /opt and
>install the bindings into there. So I'd rather see the old behavior.
Yes, but the majority of the users won't have a customized their version
of python to accept packages from the
/usr/local/lib/python2.2/site-packages as this behavior is incorrect,
only a version of python installed to /usr/local should use these
packages. The python convention is for default packages is to sit in
/usr/lib/python2.2 and additional packages that you add that are
specific to python's version go in /usr/lib/python2.2/site-packages,
packages which are version independent should go in /usr/lib/site-python.

See this thread for more info:
And this doc:

If you don't have access to /usr/lib, you should be installing your
packages into your home directory via "python setup.py install --home=~"
, not "--prefix /usr/local" as per this from the distutils page:

"The ``prefix scheme'' is useful when you wish to use one Python
installation to perform the build/install (i.e., to run the setup
script), but install modules into the third-party module directory of a
different Python installation (or something that looks like a different
Python installation). If this sounds a trifle unusual, it is--that's why
the ``home scheme'' comes first. However, there are at least two known
cases where the prefix scheme will be useful."

See this doc for more info

>Also, I'm not a python user, so couldn't the install-swig-py-ext target
>just depend upon swig-py-ext? In your patch, the install doesn't depend
>upon swig-py-ext. I'm guessing that the `install' command also does the
>`build' command?
Yeah, it could be done either way. The distutils docs mention to run
"python setup.py install", not build then install.

See this doc: http://www.python.org/doc/current/inst/standard-install.html

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 11 19:46:26 2002

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