[libvirt] Python script and extension module directory handling

[Daniel Veillard]

On Sat, Dec 12, 2009 at 11:12:31AM +0000, Daniel P. Berrange wrote:
> On Sat, Dec 12, 2009 at 12:47:46AM +0100, Matthias Bolte wrote:
> 
> > From 1f5083be1dcbf6877dfbae44e9ea4e50ebaec708 Mon Sep 17 00:00:00 2001
> > From: Matthias Bolte <matthias.bolte at googlemail.com>
> > Date: Sat, 12 Dec 2009 00:11:31 +0100
> > Subject: [PATCH] Fix install location for Python bindings
> > 
> > Commit 66137344feb488ea87b0d92f3c03844d9a7a7786 changed the Python detection
> > mechanism in configure to use AM_PATH_PYTHON. This results in a changed
> > install location for the Python bindings, at least on Fedora 12 64bit systems.
> > 
> > Before this commit libvirt.py and libvirtmod.so were installed to
> > 
> >   /usr/lib64/python2.6/site-packages
> > 
> > After this commit they are installed to
> > 
> >   /usr/lib/python2.6/site-packages
> > 
> > Mixed Python packages (containing *.py and *.so files) should be installed to
> > the pyexecdir directory detected by AM_PATH_PYTHON.
> > 
> > This restores the install location from before the AM_PATH_PYTHON commit.
> > 
> > * configure.in: remove unnecessary pythondir export
> > * python/Makefile.am: switch from pythondir to pyexecdir
> 
> ACK this looks correct to me.

  ACK I was wondering a bit about the location for the .py, but I
  prefer this approach,

    thanks !

Daniel

-- 
Daniel Veillard      | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
daniel at veillard.com  | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library  http://libvirt.org/