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

List:       kde-devel
Subject:    Re: running two versions of kde
From:       John Gluck <jgluckca () rogers ! com>
Date:       2004-01-28 4:57:38
Message-ID: 40174142.8000708 () rogers ! com
[Download RAW message or body]

Hi

I keep 2 or three versions of kde around...
My approach is simple.
Under /opt I create a directory for the kde version say kde-3.1.5 and 
kde3.2rc1. After I have everything built, I simple create a softlink to 
the version I want to run. Something like this: ln -s /opt/kde3.2rc1 kde
In my /etc/profile, I make sure the search path has /opt/kde/bin and not 
the specific version.

When the system starts, it will look for /opt/kde/bin but since this is 
a link to the version I want to run, that is what it picks up. The only 
reason I keep an old version is as a fallback in case the new version is 
really broken. I have yet to have a Kde that is so broken I want to go 
back. The kde guys do a pretty good job.

When I build a new version, I am running my current version of kde and 
just do a ./configure --prefix=kde3.2rc1 (for example) then evrything 
installs in a new directory.

John

Luiz Eduardo Guida Valmont wrote:
> i have been wondering whether or not i could keep kde 3.1.5 and kdecvs on the 
> same machine; while i have come with a simple answer which is basically the 
> that's described at http://developer.kde.org/build/build2ver.html, i have an 
> extra command you could issue in order to avoid one version trying to load 
> the other's libs;
> 
> i have once tryied building a linux from scratch and, from the lfs book, i 
> quote this (it will become clearer): "Notice that /tools/bin comes last in 
> the PATH. This means that a temporary tool will not be used any more as soon 
> as its final version is installed. Well, at least when the shell doesn't 
> remember the locations of executed binaries -- for this reason hashing is 
> switched off a bit further on."
> 
> this is the command: "exec /tools/bin/bash --login +h"
> 
> "Note the use of the +h directive. This tells bash not to use its internal 
> path hashing. Without this directive, bash would remember the paths to 
> binaries it has executed. Since we want to use our newly compiled binaries as 
> soon as they are installed, we turn off this function for the duration of 
> this chapter."
> 
> well, this is it; with this command (and $KDEDIR/bin from the cvs before the 
> $PATH - like "%KDEDIR/bin:$PATH") then you won't run the risk of issuing kate 
> while in the cvs session and end up running the stable kate...
> 
> hope this helps,
> Luiz Eduardo Guida Valmont
> 
>  
> 
>>>Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>>
> 


 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]