Bug 183291 - kdelibs python modules do not install cleanly to non-systemwide directories
Summary: kdelibs python modules do not install cleanly to non-systemwide directories
Status: RESOLVED DUPLICATE of bug 174806
Alias: None
Product: bindings
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-05 12:53 UTC by Frank Hellmuth
Modified: 2009-02-05 12:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Hellmuth 2009-02-05 12:53:29 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I'm running a system wide kde 4.2 installation and a SVN version build by kdesvn-build ind my test users home directory. Installing kdelibs fails with:

-- Installing: /usr/lib64/python2.5/site-packages/PyKDE4/plasmascript.py
CMake Error at workspace/plasma/scriptengines/python/cmake_install.cmake:60 (FILE):
  file INSTALL cannot copy file
  "/home/fhellmut/kdesvn/kdebase/workspace/plasma/scriptengines/python/plasmascript.py"
  to "/usr/lib64/python2.5/site-packages/PyKDE4/plasmascript.py".
Call Stack (most recent call first):
  workspace/plasma/scriptengines/cmake_install.cmake:40 (INCLUDE)
  workspace/plasma/cmake_install.cmake:42 (INCLUDE)
  workspace/cmake_install.cmake:76 (INCLUDE)
  cmake_install.cmake:39 (INCLUDE)

Would it be possible to avoid these conflicts between the system wide and user installation by using Python's environment variables PYTHONHOME and PYTHONPATH?

It looks like I'm not the only user experiencing that problem: See the corresponding thread in the kde forums:

http://forum.kde.org/cmake-error-make-installing-kdebase-80-t-16779.html
Comment 1 Pino Toscano 2009-02-05 12:59:29 UTC

*** This bug has been marked as a duplicate of bug 174806 ***