1 |
----- Original Message ---- |
2 |
|
3 |
> From: Dale <rdalek1967@×××××.com> |
4 |
> To: gentoo-user@l.g.o |
5 |
> chrome://messenger/locale/messengercompose/composeMsgs.properties: |
6 |
> > On 02/26/2010 06:06 AM, BRM wrote: |
7 |
> >> I am quite happy with KDE4 - presently using KDE 4.3.5. I still have KDE |
8 |
> 3.5.10 installed, and am wondering how much longer I need to keep it around...I |
9 |
> probably use all KDE4 apps, though there might be a few here or there that I use |
10 |
> on a rare occasion that are still KDE3 based...may be...and no, I don't plan on |
11 |
> using KDE Sunset Overlay[1] |
12 |
> >> Any how...I'm wondering what the best method to remove KDE3.5 safely is: |
13 |
> >> 1) Just leave it and may be it'll just get removed? |
14 |
> >> 2) Found this entry on removing it |
15 |
> http://linuxized.blogspot.com/2008/10/how-to-unmerge-kde-3-packages-if-their.html |
16 |
> >> But nothing registers as a 'dup' even though qlist does show a lot of KDE |
17 |
> 3.5.10 packages installed. (Yeah, I'd need to modify the line to ensure it |
18 |
> doesn't remove KDE 4.3.5). |
19 |
> >> 3) Gentoo KDE4 guide suggests a method, but it seems to be more related to |
20 |
> removing KDE entirely... |
21 |
> >> http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml |
22 |
> > If you keep your world file (/var/lib/portage/world) tidy, simply deleting all |
23 |
> lines with KDE3 packages and running emerge -a --depclean will take care of it. |
24 |
> > You *do* keep your world file tidy, don't you? :P |
25 |
> That would be the easiest method. If you use the kde-meta package like I do, |
26 |
> just remove the one for KDE 3 and let --depclean do its thing. It should get |
27 |
> all of it. |
28 |
|
29 |
I actually don't touch the world file, and just do the 'emerge world -vuDNa' for updates. |
30 |
From my POV, that is emerge/Portage's job - not mine. |
31 |
|
32 |
Aside from that, I'm not sure I have ever really run "emerge --depclean", but I also |
33 |
rarely uninstall anything, but don't install things left or right to try out either, so |
34 |
typically upgrades are all I need to do. |
35 |
|
36 |
Having just done a compiler upgrade, I can say that there are roughly 1100 packages (emerge -eav) in world that were recompiled. |
37 |
|
38 |
I was just contemplating - KDE4 is stable, and I don't see myself running KDE3 again; so why keep it around. |
39 |
If 'emerge world -vuDNa' will remove it when it gets pushed off the main trunk, then that's probably fine with me - since that seems to not be very far out now. |
40 |
If not, then I definitely want to remove it now as there is no other reason for keeping it around. |
41 |
|
42 |
> If you want to keep something tho, you need to add it to the world file first |
43 |
> and then run --depclean. That way it will keep the program(s) you want and the |
44 |
> things they depend on but remove everything else. This will save you from |
45 |
> having to reinstall those packages. You may even have to get them from the |
46 |
> overlay at that point. So don't uninstall something you want to keep. |
47 |
|
48 |
That's the only issue. My only concern is software (e.g. KDevelop) that may not have been updated to KDE4 yet. (Not a fan of KDevelop3; waiting to see how KDevelop4 is going to shape up.) |
49 |
|
50 |
> If you have the drive space, you can leave it there for a while longer tho. |
51 |
> Just keep in mind that there are no security updates or anything like that. If |
52 |
> you add the overlay, you will get a few updates at least. |
53 |
|
54 |
I do have the disk space on the systems I have KDE3 and KDE4 on; so that's not a concern. |
55 |
|
56 |
Ben |