KDE3 Beta2/SuSE7.3
Will the installation of the beta rpms from the SuSE ftp site allow this installation installation to coexist with a previous KDE 2.2.2 installation or should KDE 3 beta2 be installed from source to facilitate that??? I would like to be able to run either at will until I'm confident I can let KDE2.2.2 go. Thank You, Anthony
On Saturday 23 February 2002 02.01, Anthony W. Marino wrote:
Will the installation of the beta rpms from the SuSE ftp site allow this installation installation to coexist with a previous KDE 2.2.2 installation or should KDE 3 beta2 be installed from source to facilitate that???
I would like to be able to run either at will until I'm confident I can let KDE2.2.2 go.
It will work perfectly, and won't disturb your kde2 setup at all. All kde2 files reside in /opt/kde2 and your local config is in ~/.kde2. The kde3 beta will land in /opt/kde3 (you can check with rpm -qpl package.rpm to make absolutely certain). If there had been any "collisions" with kde2 programs rpm would have warned you (file "foo" from package kdebase3.rpm collides with file "foo" from package kdebase.rpm, or words to that effect). Also, to make sure the config files are separate, the variable KDEHOME decides where they land. It is set in /opt/kde3/bin/startkde, so edit that to satisfy yourself that everything is OK. There are only two things I can think of that kde2 and kde3-beta uses and that's ~/KDesktop and ~/Mail. KDesktop is all your desktop links and icons, and Mail is where kmail stores your mail. But if you, like me, are truly paranoid about these things, create a test user and log in as that user to try out kde3. I have one user set for kde3 and one for gnome2 (where are the rpms, suse?). That way I can be sure of never messing up my "main" account. regards Anders
Suse 7.1 kernel 2.4.17 Reading the Kde3 posts has stimulated my interest. Can I upgrade from a lowly kde 2.1.2 from the ftp.suse.com supplementary directory ? Or will I have to look for additional files e.g. upgrade Qt. Brian Marr On Saturday 23 February 2002 11:52, you wrote:
On Saturday 23 February 2002 02.01, Anthony W. Marino wrote:
Will the installation of the beta rpms from the SuSE ftp site allow this installation installation to coexist with a previous KDE 2.2.2 installation or should KDE 3 beta2 be installed from source to facilitate that???
I would like to be able to run either at will until I'm confident I can let KDE2.2.2 go.
It will work perfectly, and won't disturb your kde2 setup at all. All kde2 files reside in /opt/kde2 and your local config is in ~/.kde2. The kde3 beta will land in /opt/kde3 (you can check with rpm -qpl package.rpm to make absolutely certain). If there had been any "collisions" with kde2 programs rpm would have warned you (file "foo" from package kdebase3.rpm collides with file "foo" from package kdebase.rpm, or words to that effect).
Also, to make sure the config files are separate, the variable KDEHOME decides where they land. It is set in /opt/kde3/bin/startkde, so edit that to satisfy yourself that everything is OK.
There are only two things I can think of that kde2 and kde3-beta uses and that's ~/KDesktop and ~/Mail. KDesktop is all your desktop links and icons, and Mail is where kmail stores your mail.
But if you, like me, are truly paranoid about these things, create a test user and log in as that user to try out kde3. I have one user set for kde3 and one for gnome2 (where are the rpms, suse?). That way I can be sure of never messing up my "main" account.
regards Anders
On Friday 22 February 2002 08:22 pm, Anders Johansson wrote:
On Saturday 23 February 2002 02.01, Anthony W. Marino wrote:
Will the installation of the beta rpms from the SuSE ftp site allow this installation installation to coexist with a previous KDE 2.2.2 installation or should KDE 3 beta2 be installed from source to facilitate that???
I would like to be able to run either at will until I'm confident I can let KDE2.2.2 go.
It will work perfectly, and won't disturb your kde2 setup at all. All kde2 files reside in /opt/kde2 and your local config is in ~/.kde2. The kde3 beta will land in /opt/kde3 (you can check with rpm -qpl package.rpm to make absolutely certain). If there had been any "collisions" with kde2 programs rpm would have warned you (file "foo" from package kdebase3.rpm collides with file "foo" from package kdebase.rpm, or words to that effect).
Also, to make sure the config files are separate, the variable KDEHOME decides where they land. It is set in /opt/kde3/bin/startkde, so edit that to satisfy yourself that everything is OK.
There are only two things I can think of that kde2 and kde3-beta uses and that's ~/KDesktop and ~/Mail. KDesktop is all your desktop links and icons, and Mail is where kmail stores your mail.
But if you, like me, are truly paranoid about these things, create a test user and log in as that user to try out kde3. I have one user set for kde3 and one for gnome2 (where are the rpms, suse?). That way I can be sure of never messing up my "main" account.
regards Anders
Some things I had to do: 1) Added a new "login/session" of "kde3" in the "Control Center" This relates to the installation entry: "/usr/X11R6/bin/kde3" which is a symlink to "/opt/kde3/bin/startkde". NOTE: The SuSE/YAST1 installation had added double forward slashes to the above "kde3" path which I removed and corrected (ie; "/usr//X11R6//bin/kde3"). 2)Updated ".xinitrc" to include a check for "kde3" windowmanager and then added the path as "/usr/X11R6/bin/kde3" to facilitate execution. Problem: I didn't have any icons on my panel with the exception of the task icon and the desktop icon. Anthony I made the changes to .xinitrc to include a check for "kde3" session (which I added in the "control
On Saturday 23 February 2002 05.28, Anthony W. Marino wrote:
Some things I had to do: 1) Added a new "login/session" of "kde3" in the "Control Center" This relates to the installation entry: "/usr/X11R6/bin/kde3" which is a symlink to "/opt/kde3/bin/startkde". NOTE: The SuSE/YAST1 installation had added double forward slashes to the above "kde3" path which I removed and corrected (ie; "/usr//X11R6//bin/kde3").
True, forgot about that. But the // is irrelevant. The shell will just ignore the extra / and handle it correctly.
2)Updated ".xinitrc" to include a check for "kde3" windowmanager and then added the path as "/usr/X11R6/bin/kde3" to facilitate execution.
Not needed. That test is for when you don't have a window manager set. Note that the tests begin with if test -z "$WINDOWMANAGER" ; then if test -x /usr/X11R6/bin/kde ; then and so forth. test -z means "if $WINDOWMANAGER is empty", so that is just a series of tests to load a "default" wm.
Problem: I didn't have any icons on my panel with the exception of the task icon and the desktop icon.
Yep, I had that too. The cvs version creates them though, so I don't know what suse's packager has done. I'm in the process of creating my own rpms, though... //Anders
On Friday 22 February 2002 11:34 pm, Anders Johansson wrote:
On Saturday 23 February 2002 05.28, Anthony W. Marino wrote:
Some things I had to do: 1) Added a new "login/session" of "kde3" in the "Control Center" This relates to the installation entry: "/usr/X11R6/bin/kde3" which is a symlink to "/opt/kde3/bin/startkde". NOTE: The SuSE/YAST1 installation had added double forward slashes to the above "kde3" path which I removed and corrected (ie; "/usr//X11R6//bin/kde3").
True, forgot about that. But the // is irrelevant. The shell will just ignore the extra / and handle it correctly.
2)Updated ".xinitrc" to include a check for "kde3" windowmanager and then added the path as "/usr/X11R6/bin/kde3" to facilitate execution.
Not needed. That test is for when you don't have a window manager set. Note that the tests begin with
if test -z "$WINDOWMANAGER" ; then if test -x /usr/X11R6/bin/kde ; then
and so forth.
test -z means "if $WINDOWMANAGER is empty", so that is just a series of tests to load a "default" wm.
Problem: I didn't have any icons on my panel with the exception of the task icon and the desktop icon.
Yep, I had that too. The cvs version creates them though, so I don't know what suse's packager has done. I'm in the process of creating my own rpms, though...
//Anders
I would be interested should you decide to distribute the rpms. Thanks for your help, Anders! Anthony
participants (3)
-
Anders Johansson
-
Anthony W. Marino
-
Brian Marr