KDE 3.3 *AND* KDE 3.4

Danuvius · Guru Joined: 18 Sep 2004 Posts: 375 Location: Toronto

I want to try out KDE 3.4, but keep KDE 3.3.

Is there a way to have them both installed at the same time?

If there is not--am I very likely to seriously ruin my system and have to reinstall KDE 3.3? (In which case, how would I be able to avoid having to recompile from source?)

Sorry for the noob questions. Thanks in advance!

mathfeel · l33t Joined: 03 Aug 2004 Posts: 700

Danuvius · Guru Joined: 18 Sep 2004 Posts: 375 Location: Toronto

ebrostig · Posted: Sun Feb 20, 2005 2:08 am Post subject:

The kde-meta package is the split ebuilds, approx 300+ some ebuilds.

If you just want the whole KDE package, just emerge kde

The 3.4 build is slotted in /usr/kde/3.4 and the 3.3 will remain function and is slotted in /usr/kde/3.3

Erik
_________________
'Yes, Firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'

Danuvius · Guru Joined: 18 Sep 2004 Posts: 375 Location: Toronto

ebrostig · Posted: Sun Feb 20, 2005 2:23 am Post subject:

kde 3.4 is in beta and masked ~arch, i.e you either need to unmask the packages in /etc/portage/package.unmask or use ~x86 in /etc/make.conf.

Erik
_________________
'Yes, Firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'

tlaloctlaloc · Posted: Sun Feb 20, 2005 7:25 am Post subject:

Just a warning:
After I installed kde-3.4 programs like kdevelop compiled against the 3.4 libraries and did not work therefore.
Bye, Valentin.

Lokheed · Posted: Sun Feb 20, 2005 9:35 am Post subject:

ebrostig · Posted: Sun Feb 20, 2005 2:33 pm Post subject:

Lokheed · Posted: Sun Feb 20, 2005 5:56 pm Post subject:

Maybe he was logged into KDE 3.4 and tried to compile the 3.3 version of KDevelop.
_________________
You're not afraid of the dark are you?

supermihi · Guru Joined: 09 Feb 2005 Posts: 348

You should install the new KDE split ebuilds instead of the monolithic ones (like kdeedu, kdebase ...). First, they are future, and second, you'll have less problems with your old kde-3.3 builds.
What I did:
List the complete /usr/portage/kde-base/ directory into /etc/portage/package.unmask and /etc/portage/package.keywords to unmask all split ebuilds. As the old monolithic builds are now unmasked too, I removed them by hand (which is less work than entering the hundreds of split ebuilds manually *g*). For me there were only two packages that I needed both for 3.3 and 3.4: arts and kdelibs. Arts should be no problem, but i think if you emerge kdelibs-3.4, any new compiled kde apps will only run with kde-3.4 - but that doesn't really matter if you only want to try kde-3.4.
I did this only in the package.unmask file, since it should be enough when a package is masked once - quick and dirty

Now I can emerge the new kde-3.4 with kdebase-startkde (this is only a basic system, for the whole kde stuff emerge kde-meta).
I didn't compile kde-3.4 yet, but the outputs of different emerge -pv... commands let me hope that it should do fine!

Here's my package.keywords:

supermihi · Guru Joined: 09 Feb 2005 Posts: 348

Sorry, I forgot to remove one of the monolithic packages: kdewebdev. It has also been replaced by some split ebuilds.[/code][/quote]
_________________
"You may say I'm a dreamer, but I'm not the only one."

tlaloctlaloc · Posted: Mon Feb 21, 2005 8:15 am Post subject:

Lokheed · Posted: Tue Feb 22, 2005 1:14 am Post subject: