[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: can't install kdebase, needs root
From:       Milian Wolff <mail () milianw ! de>
Date:       2010-06-12 14:11:16
Message-ID: 201006121611.17213.mail () milianw ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Arno Rehn, 12.06.2010:
> On Saturday 12 June 2010 15:36:35 Michael Jansen wrote:
> > On Samstag 12 Juni 2010 15:25:50 Milian Wolff wrote:
> > > Michael Jansen, 12.06.2010:
> > > > On Samstag 12 Juni 2010 00:49:56 Ben Cooksley wrote:
> > > > > On Sat, Jun 12, 2010 at 10:41 AM, Matthew Woehlke
> > > > > 
> > > > > <mw_triad@users.sourceforge.net> wrote:
> > > > > > I've started getting this the last two days:
> > > > > > 
> > > > > > CMake Error at
> > > > > > workspace/plasma/generic/scriptengines/python/cmake_install.cmake
> > > > > > :7 6 (FILE): file cannot create directory:
> > > > > > /usr/lib64/python2.6/site-packages/PyKDE4. Maybe need
> > > > > > administrative privileges.
> > > > > > 
> > > > > > The line in question (trying to install to
> > > > > > ${PYTHON_SITE_PACKAGES_DIR}) seems to have been there for some
> > > > > > time, so I am not sure what has changed (I think, though, PyKDE
> > > > > > was not being built before on my system, though again, I don't
> > > > > > know why that would have changed).
> > > > > 
> > > > > Passing the following argument to CMake when configuring kdebase
> > > > > should be sufficient..
> > > > > 
> > > > > -DPYTHON_SITE_PACKAGES_DIR=$KDEDIR/lib/python2.6/site-packages
> > > > 
> > > > OR -DPYTHON_LIBS_WITH_KDE_LIBS=True
> > > > 
> > > > Which is defined in FindPythonLibrary.cmake (kdelibs/cmake/modules)
> > > > and makes sure everything is installed into PREFIX according to the
> > > > used python version. But is hard to find because it is not
> > > > documented and cached in CMakeCache.txt.
> > > 
> > > could this be made the default?
> > 
> > IMHO it not only could be made the default but has to be the default. I
> > already told cmake to install everything  into CMAKE_INSTALL_PREFIX and
> > expect it to do that. But having read the discussion that happened the
> > last time this was discussed i certainly won't change anything.
> 
> I wouldn't make it the default. After all, the Python bindings won't work
> if they're not installed into the correct directory. I'd put a big fat
> warning/info message at the end of cmake configuring, so everyone who
> wants to install KDE somewhere else (and the Python bindings with it),
> know what to do.
> 
> Currently all of these variables seem pretty undocumented to me, so it's
> not unusual that people don't know what to do. Adding something as simple
> as
> 
> "INFORMATION: The Python bindings are going to be installed to
> ${PYTHON_SITE_PACKAGES_DIR}. If you don't have enough permissions to
> install them there or want them somewhere else, set
> PYTHON_LIBS_WITH_KDE_LIBS=True or PYTHON_SITE_PACKAGES_DIR."
> 
> and there shouldn't be any misunderstandings anymore. Just my 2 cents.

And you should tell them what to do in order to get the bindings working, if 
that doesn't work in the other directories...
-- 
Milian Wolff
mail@milianw.de
http://milianw.de

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]