2009/4/11 Thiago Macieira <[email protected]>: > > Well, if we detect Python 2.6, then we should install to the KDE prefix by > default. The problem then is, of course, the surprise factor: if someone > upgrades, suddenly KDE starts installing to the wrong path. > > I recommend, instead, that we default to the KDE prefix and, if Python 2.5 > or earlier is detected, we print a big warning at the end of the cmake > run, saying that you will not be able to run and that you should set the > PYTHON_SITE_PACKAGES_DIR variable instead. Even make it a fatal error.
I have already done ALL of this work. Did nobody read my patches? I have been too busy to to clean up the asthaetic issues that have kept it out of trunk, but I honestly believe that my solution is the fullest and most superior suggestion (and implementation) yet. Please take a look. _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
