Python site packages

[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: Use -DINSTALL_PYTHON_FILES_IN_PYTHON_PREFIX=TRUE.
> 
> I considered your change a step backwards right when you sent your original
> mail about it. I didn't dare complaining because I wasn't sure whether it'd
> actually break anything for us packagers, but seeing how it breaks things
> for Debian/Ubuntu, I can only stronly urge you to revert that unhelpful
> change, or at least make INSTALL_PYTHON_FILES_IN_PYTHON_PREFIX the default.
> 

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.

Christophe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20130117/55ddbd36/attachment.sig>