Re: Python site packages

2013-01-20 Thread Michael Jansen
On Sunday, January 20, 2013 08:37:28 PM Ben Cooksley wrote: On Sun, Jan 20, 2013 at 12:55 PM, Kevin Kofler kevin.kof...@chello.at wrote: On Saturday 19 January 2013 at 22:33:19, David Faure wrote: Because this breaks make install for developers. (For the recommended case of installing as

Re: Python site packages

2013-01-20 Thread Albert Astals Cid
El Diumenge, 20 de gener de 2013, a les 00:55:35, Kevin Kofler va escriure: On Saturday 19 January 2013 at 22:33:19, David Faure wrote: Because this breaks make install for developers. (For the recommended case of installing as user rather than as root). The default should make it easy

Re: Python site packages

2013-01-20 Thread Kevin Kofler
On Sunday 20 January 2013 at 16:11:54, Michael Jansen wrote: How about we make all of them happy? Your patch looks like the correct fix, can we please get this committed? Kevin Kofler ___ release-team mailing list release-team@kde.org

Re: Python site packages

2013-01-19 Thread David Faure
On Friday 18 January 2013 11:01:50 Vadim Zhukov wrote: 18.01.2013 1:25 пользователь Kevin Kofler kevin.kof...@chello.at написал: On Thursday 17 January 2013 at 22:14:48, Christophe Giboudeaux wrote: Well, this is exactly what this option fixed. The previous behaviour was just wrong:

Re: Python site packages

2013-01-19 Thread Kevin Kofler
On Saturday 19 January 2013 at 22:33:19, David Faure wrote: Because this breaks make install for developers. (For the recommended case of installing as user rather than as root). The default should make it easy for everyone who wants to contribute to KDE. But that makes things harder for

Re: Python site packages

2013-01-19 Thread Ben Cooksley
On Sun, Jan 20, 2013 at 12:55 PM, Kevin Kofler kevin.kof...@chello.at wrote: On Saturday 19 January 2013 at 22:33:19, David Faure wrote: Because this breaks make install for developers. (For the recommended case of installing as user rather than as root). The default should make it easy for

Re: Python site packages

2013-01-18 Thread Vadim Zhukov
18.01.2013 1:25 пользователь Kevin Kofler kevin.kof...@chello.at написал: On Thursday 17 January 2013 at 22:14:48, Christophe Giboudeaux wrote: Well, this is exactly what this option fixed. The previous behaviour was just wrong: Files should never be installed outside CMAKE_INSTALL_PREFIX

Re: Python site packages

2013-01-18 Thread Torgny Nyblom
On Friday 18 January 2013 11.01.50 Vadim Zhukov wrote: 18.01.2013 1:25 пользователь Kevin Kofler kevin.kof...@chello.at написал: On Thursday 17 January 2013 at 22:14:48, Christophe Giboudeaux wrote: Well, this is exactly what this option fixed. The previous behaviour was just wrong:

Python site packages

2013-01-17 Thread Jonathan Riddell
FindPythonLibrary.cmake seems to have changed between 4.9.97 and 4.9.98 it now incorrectly hardcodes the directory site-packages. Python 2.7 at least in Debian land uses dist-packages so it puts files into the wrong directory. Reverting back to FindPythonLibrary.cmake from 4.9.97 makes the issue

Re: Python site packages

2013-01-17 Thread Christophe Giboudeaux
On Thursday 17 January 2013 18:13:20 Jonathan Riddell wrote: FindPythonLibrary.cmake seems to have changed between 4.9.97 and 4.9.98 it now incorrectly hardcodes the directory site-packages. site-packages is the default subdir for modules, See http://docs.python.org/2/install/index.html.

Re: Python site packages

2013-01-17 Thread Christophe Giboudeaux
On Thursday 17 January 2013 21:52:58 Kevin Kofler wrote: Hi, On Thursday 17 January 2013 at 21:14:44, Christophe Giboudeaux wrote: Anyway, unless the kde-packagers list became write-only or noone takes care of the moderation queue, an email (well, two) was sent and gives the solution:

Re: Python site packages

2013-01-17 Thread Kevin Kofler
On Thursday 17 January 2013 at 22:14:48, Christophe Giboudeaux wrote: Well, this is exactly what this option fixed. The previous behaviour was just wrong: Files should never be installed outside CMAKE_INSTALL_PREFIX by default. Packagers shall use INSTALL_PYTHON_FILES_IN_PYTHON_PREFIX if