On Friday 18 January 2013 11.01.50 Vadim Zhukov wrote: > 18.01.2013 1:25 пользователь "Kevin Kofler" <[email protected]> > > написал: > > 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 as Christophe said it is wrong, if a PREFIX is specified then everything should be installed inside that. /Regards Torgny _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
