On 21 June 2010 22:04, Andreas Pakulat <[email protected]> wrote: > On 21.06.10 21:36:13, Alexander Neundorf wrote: >> Uh, yeah, and it's somewhat ugly too. >> Can we find a better solution to this ? >> I think the last time we discussed some python stuff on kde-buildsystem I >> didn't recognize a real conclusion, I was mostly confused at the end. >> >> So, if we install python modules, where should they go by default ? > > Well, thats the problem, either they're installed in a way such that > python finds them (and that usually means installing needs root-rights) > or the buildsystem obeys the prefix thats set for the project > (implicitly or by cmake-variable) in which case the user will have to > tell its python to look in an additional place. Its very similar to > installing libraries outside a directory thats mentioned in > /etc/ld.so.conf, you can do that but you'll have to set an envvar at > least to give the linker a clue where to look. With shared libs on Linux > you have a bit better way using RPATH/RUNPATH, but that doesn't really > exist for Python.
Well, as of Python 2.6 you can place Python modules under ~/.local and Python will find them correctly [1]. So really that should be factored into the defaults somehow. -- Matt Williams http://milliams.com [1] http://docs.python.org/whatsnew/2.6.html#pep-370-per-user-site-packages-directory _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
