Michael Witten wrote: >2009/4/11 Thiago Macieira <[email protected]>: >> Why can't the user set PYTHONPATH? > >Unfortunately, this must be done if you're using python < 2.6 and >installing anywhere but the system-wide site-packages. However, in >general, this is not a solution, and it is always the wrong mentality. >Always.
I see.
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.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
