--===============1753712712==
Content-type: multipart/signed; boundary=nextPart1999476.aR3KrvYhPe;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart1999476.aR3KrvYhPe
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Michael Witten wrote:
>2009/4/11 Thiago Macieira <thiago@kde.org>:
>> 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=
=20
default. The problem then is, of course, the surprise factor: if someone=20
upgrades, suddenly KDE starts installing to the wrong path.

I recommend, instead, that we default to the KDE prefix and, if Python 2.5=
=20
or earlier is detected, we print a big warning at the end of the cmake=20
run, saying that you will not be able to run and that you should set the=20
PYTHON_SITE_PACKAGES_DIR variable instead. Even make it a fatal error.

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--nextPart1999476.aR3KrvYhPe
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBJ4LT6M/XwBW70U1gRAuqvAJ9sk38yS5JyZTx66SIeuOHJKE8Q1gCgo4ov
btqOuAUX7oWepCCvvcqg8Ag=
=Auly
-----END PGP SIGNATURE-----

--nextPart1999476.aR3KrvYhPe--

--===============1753712712==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem

--===============1753712712==--