*replacing* older KDE instead of installing both?

Gentook

Hi all. I originally upgraded from a kde 3.1.5 to a beta(masked) 3.2. At that point I had (by emerge search and etcat) both editions installed.

But the new one was the one being used to no problem. I just emerged the (released) 3.2.1 and now have noticed that (by emerge search or etcat -v) that 3.1.5 is no longer reported as being installed.

But /usr/kde/3.1 is still full of 180 meg of software. Why is the software still there but the portage db claiming it's not?

Also, my emerge syncs thrash a bit these days. Is it a good idea to remove the whole portage db and re-sync?

Best wishes to all,
G

rob512 · n00b Joined: 13 Oct 2003 Posts: 23

when i went from 3.1.5 to 3.2 i just deleted my /usr/kde/3.1 directory. actually i renamed it first to make sure it wouldn't break anything, then just deleted it after everything worked fine.

i'm sure this is not the best way to get rid of the old stuff, but i wanted to clear up some space. i did have to re-emerge mplayer afterward. i think it was probably using a library or something that i deleted.

does anybody have a better/safer way to do this? i'm going to move to 3.2.1 i the next few days so i will need to get rid of my old 3.2 stuff soon.

c4Ff3In3 4ddiC+ · Tux's lil' helper Joined: 16 Aug 2003 Posts: 110

emerge will upgrade KDE 3.2.0 to KDE 3.2.1, so you shouldn't have anything to worry about. You will probably want to run revdev-rebuild afterwards to catch any programs that are broken due to library upgrades.

Gentook · Posted: Sat Mar 13, 2004 9:17 pm Post subject:

No look. I upgraded to 3.2 while it was still masked/beta. The 3.1.5 was left around. I then had 2 kde's installed. Now that I upgraded from 3.2 to 3.2.1(released) emerge/etcat doesn't think I have 3.1.5 anymore but the files are still there.

Was just wondering if someone could explain this.

Best wishes,
G

jmb65 · n00b Joined: 01 Nov 2003 Posts: 14 Location: UK

I'm pretty certain that if you didn't do a "emerge unmerge" then kde 3.1.x will still be lying around.

What might be happening is that etcat will ONLY list packages that have an entry in the CURRENT portage tree.

For example, I have gtk+-2.2.1 installed on my machine, but the ebuilds for this have been removed from the current portage tree. If I do "etcat -v gtk+" I get:

------
[ Results for search key : gtk+ ]
[ Candidate applications found : 3 ]

Only printing found installed programs.

* x11-libs/gtk+-1.2.10-r10 :
[ I] 1.2.10-r10 (1)

* x11-libs/gtk+-1.2.10-r11 :
[M~ ] 1.2.10-r11 (1)

* x11-libs/gtk+-2.2.4-r1 :
[ ] 2.2.4-r1 (2)
------

Thus it look like I only have gtk+-1 installed not gtk+-2.
However, qpkg tells the whole story, doing "qpkg -v gtk+" I get,

------
x11-libs/gtk+-1.2.10-r10 *
x11-libs/gtk+-2.2.1 *
x11-libs/gtk+extra-0.99.17 *
x11-libs/gtk+-1.2.10-r10
x11-libs/gtk+-2.2.4-r1
x11-libs/gtk+-1.2.10-r11
x11-libs/gtk+extra-0.99.17
------

Thus if I were you I would try "qpkg -v kde", then if kde-3.1.x is still there, you should be able to remove it with "emerge unmerge kde-3.1.x".

Just make sure to substitute x with the exact version number, including the ebuild revision number that qpkg reports.

Gentook · Posted: Sun Mar 14, 2004 12:36 am Post subject:

Hey, thank you. This is exactly the explanation I was trying to find out. Thanks man.