Python site packages

[David Faure]

On Friday 18 January 2013 11:01:50 Vadim Zhukov wrote:
> 18.01.2013 1:25 пользователь "Kevin Kofler" <kevin.kofler at 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 by default.
> > > 
> > > Packagers shall use INSTALL_PYTHON_FILES_IN_PYTHON_PREFIX if their
> 
> python
> 
> > > packages are built with exotic paths.
> > 
> > Maybe a reasonable strategy would be to default to
> > INSTALL_PYTHON_FILES_IN_PYTHON_PREFIX if PREFIX is /usr?
> 
> ... Thus hardcoding another path? What about OSes (including some Linux
> distros, not even talking about *BSDs) that use /usr/local or ever /opt?
> 
> Why not to use INSTALL_PYTHON_FILES_IN_PYTHON_PREFIX by default and thus be
> backward-compatible?

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.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5