Questions about "make install"
Mike Meyer
mwm at mired.org
Fri Aug 13 12:51:29 UTC 2010
On Fri, 13 Aug 2010 14:44:47 +0200
Paul Boddie <paul.boddie at biotek.uio.no> wrote:
> Martin Geisler wrote:
> > Paul Boddie <paul.boddie at biotek.uio.no> writes:
> >
> >> Modifying sys.path is the way to go, in my opinion. You frequently
> >> have to do this when installing stand-alone Python applications.
> >>
> >
> > Right, so let us see if we can automate this as part of 'make install'.
> >
>
> Actually, since distutils changes the #! line of the hg program to point
> to the specific Python executable used during installation, and since
> distutils puts the libraries into the site-packages of that Python
> executable's installation, I'm now not too sure any sys.path fixes are
> necessary. You'd certainly need to change your PATH after doing an
> installation into some non-central place (including /usr/local), but
> Python should know where its site-packages are, and thus find the
> mercurial package.
That only works if you let distutils put things in python's
site-packages directory. "make install" sets the PREFIX to /usr/local,
which may or may not be somewhere where Python will look.
<mike
--
Mike Meyer <mwm at mired.org> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
More information about the Mercurial
mailing list