[PATCH] bug 174806

[Alexander Neundorf]

On Saturday 11 April 2009, Thiago Macieira wrote:
> Michael Witten wrote:
> >2009/4/11 Thiago Macieira <thiago at 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
> 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.

If the effect will be that it will build fine, but not run except some special 
env. vars. are set at runtime, it should not be a fatal error.

Alex