[PyKDE] Root vs. non-root builds

[Ricardo Javier Cardenes Medina]

On Fri, Aug 23, 2002 at 08:17:09AM -0700, Jim Bublitz wrote:
> On 23-Aug-02 Ricardo Javier Cardenes Medina wrote:
> > On Thu, Aug 22, 2002 at 10:27:11PM -0700, Jim Bublitz wrote:
> > Well... The only reason for being root at compile time is that
> > right now you're looking for libqtcmodule.so to find out which
> > Qt version (threaded or not) PyQt were compiled against. You
> > expect it to be in the same place where PyKDE is to be installed
> > (modDir), and that is often the site-packages inside your
> > favorite Python version's directory, which uses to be owned by
> > root.
> 
> Nope, that behaviour occurs in build.py which doesn't require root
> privs - all of the relevant directories are world readable. I

Er... Yes, that's true. I explained it bad. Of course, there's no problem
at all _reading_ the files but when, once compiled, you try to install
the files on that place (which is owned by root) :-), as you noticed.

> > I'll send you later a tiny patch with the changes I've made for
> > this behaviour.
> 
> I'll watch for that - I'm always interested in improvements.

I've compiled PyKDE applying the second patch I sent to the list this
morning. No problems so far. I did:

python2.1 build.py
	-d /the/fake/inst/directory/while/building/package
        -s /usr/lib/python2.1/site-packages

So, now it looks for sip and PyQt modules at
/usr/lib/python2.1/site-packages, and installs PyKDE's modules at the
other directory. Without that tiny change, build.py would search for
libtq* on the PyKDE installation path.