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

List:       kde-devel
Subject:    Re: Running KDE 4 programs in a KDE 3 session
From:       Benjamin Meyer <ben () meyerhome ! net>
Date:       2005-09-09 14:46:24
Message-ID: 200509091102.38033.ben () meyerhome ! net
[Download RAW message or body]

On Friday 09 September 2005 9:28 am, Frans Englich wrote:
> On Thursday 08 September 2005 10:01, David Faure wrote:
> > On Tuesday 06 September 2005 13:56, Thiago Macieira wrote:
> > > Frans Englich wrote:
> > > >I'm having trouble running KDE 4 programs in a KDE 3 session, which I
> > > > think should be possible.
> > >
> > > It isn't. Sorry, don't try what you're trying.
> > >
> > > In the future, we may come up with a way of making it possible, but it
> > > currently isn't. If you start a KDE4 program in a KDE3 session, you
> > > will very likely break it and have to log out and back in.
> >
> > Hmm? I do it all the time.
>
> Yeah, I suspected it. It was so obvious the different KSycoca versions were
> fighting the same db file.
>
> > The important thing is to adjust environment variables so that the kde4
> > stuff doesn't mess up the kde3 stuff.
> >
> > See setup-env, which used to be in the kde4 branch:
> >
> > # Ensure PATH and LD_LIBRARY_PATH point to qt4, then do the following:
> > export KDEHOME=$HOME/.kde4
> > export KDETMP=/tmp/$USER-kde4
> > mkdir -p $KDETMP
> >
> > export KDEVARTMP=/var/tmp/$USER-kde4
>
> I missed that one, and that's why it didn't work.
>
>
> Thanks,
>
> 		Frans

The best solution I have found is to just have another account on my system 
that I use.  I then just ssh localhost into my machine.  This prevents svn 
from corrupting my home directory.  It works for the majority of my 
development work.

-Benjamin Meyer

-- 
aka icefox
Public Key: http://www.icefox.net/public_key.asc
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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