1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
2 |
> ----- Original Message ---- |
3 |
> |
4 |
> |
5 |
>> From: Dale<rdalek1967@×××××.com> |
6 |
>> To: gentoo-user@l.g.o |
7 |
>> chrome://messenger/locale/messengercompose/composeMsgs.properties: |
8 |
>> |
9 |
>>> On 02/26/2010 06:06 AM, BRM wrote: |
10 |
>>> |
11 |
>>>> I am quite happy with KDE4 - presently using KDE 4.3.5. I still have KDE |
12 |
>>>> |
13 |
>> 3.5.10 installed, and am wondering how much longer I need to keep it around...I |
14 |
>> probably use all KDE4 apps, though there might be a few here or there that I use |
15 |
>> on a rare occasion that are still KDE3 based...may be...and no, I don't plan on |
16 |
>> using KDE Sunset Overlay[1] |
17 |
>> |
18 |
>>>> Any how...I'm wondering what the best method to remove KDE3.5 safely is: |
19 |
>>>> 1) Just leave it and may be it'll just get removed? |
20 |
>>>> 2) Found this entry on removing it |
21 |
>>>> |
22 |
>> http://linuxized.blogspot.com/2008/10/how-to-unmerge-kde-3-packages-if-their.html |
23 |
>> |
24 |
>>>> But nothing registers as a 'dup' even though qlist does show a lot of KDE |
25 |
>>>> |
26 |
>> 3.5.10 packages installed. (Yeah, I'd need to modify the line to ensure it |
27 |
>> doesn't remove KDE 4.3.5). |
28 |
>> |
29 |
>>>> 3) Gentoo KDE4 guide suggests a method, but it seems to be more related to |
30 |
>>>> |
31 |
>> removing KDE entirely... |
32 |
>> |
33 |
>>>> http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml |
34 |
>>>> |
35 |
>>> If you keep your world file (/var/lib/portage/world) tidy, simply deleting all |
36 |
>>> |
37 |
>> lines with KDE3 packages and running emerge -a --depclean will take care of it. |
38 |
>> |
39 |
>>> You *do* keep your world file tidy, don't you? :P |
40 |
>>> |
41 |
>> That would be the easiest method. If you use the kde-meta package like I do, |
42 |
>> just remove the one for KDE 3 and let --depclean do its thing. It should get |
43 |
>> all of it. |
44 |
>> |
45 |
> I actually don't touch the world file, and just do the 'emerge world -vuDNa' for updates. |
46 |
> > From my POV, that is emerge/Portage's job - not mine. |
47 |
> |
48 |
> Aside from that, I'm not sure I have ever really run "emerge --depclean", but I also |
49 |
> rarely uninstall anything, but don't install things left or right to try out either, so |
50 |
> typically upgrades are all I need to do. |
51 |
> |
52 |
> Having just done a compiler upgrade, I can say that there are roughly 1100 packages (emerge -eav) in world that were recompiled. |
53 |
> |
54 |
> I was just contemplating - KDE4 is stable, and I don't see myself running KDE3 again; so why keep it around. |
55 |
> 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. |
56 |
> If not, then I definitely want to remove it now as there is no other reason for keeping it around. |
57 |
> |
58 |
> |
59 |
>> If you want to keep something tho, you need to add it to the world file first |
60 |
>> and then run --depclean. That way it will keep the program(s) you want and the |
61 |
>> things they depend on but remove everything else. This will save you from |
62 |
>> having to reinstall those packages. You may even have to get them from the |
63 |
>> overlay at that point. So don't uninstall something you want to keep. |
64 |
>> |
65 |
> 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.) |
66 |
> |
67 |
> |
68 |
>> If you have the drive space, you can leave it there for a while longer tho. |
69 |
>> Just keep in mind that there are no security updates or anything like that. If |
70 |
>> you add the overlay, you will get a few updates at least. |
71 |
>> |
72 |
> I do have the disk space on the systems I have KDE3 and KDE4 on; so that's not a concern. |
73 |
> |
74 |
> Ben |
75 |
> |
76 |
> |
77 |
|
78 |
Another reason the question of keeping your world file clean could come |
79 |
up, do you use the --oneshot option when needed? This can really junk |
80 |
up a world file. Let's say kde-meta pulls in konqueror. For some |
81 |
reason, you need to re-emerge konqueror and do so without the --oneshot |
82 |
option. Now, konqueror is listed in the world file when it really |
83 |
shouldn't be there. This can happen with hundreds of other packages as |
84 |
well. I fell for this ages ago myself because I didn't know about |
85 |
this. So, even tho you may not touch the world file, it could still |
86 |
have packages listed in there that are not needed. It sort of creeps up |
87 |
on you if you are not careful. The biggest thing portage does with |
88 |
world is add stuff and keep it in alphabetical order. |
89 |
|
90 |
There are some things that should be done to keep a sane system in my |
91 |
opinion. --depclean is one of them. Running revdep-rebuild is |
92 |
another. I even go look at my world file from time to time to see if I |
93 |
forgot to use the --oneshot option myself. Gentoo is like anything |
94 |
else, it has to be maintained. The better maintenance you do the better |
95 |
things will be. After all, there will be problems no matter what you |
96 |
do but keeping it sane helps. Your mileage may vary tho. |
97 |
|
98 |
If you want to keep the Kdevelop 3 around, just add it to world. |
99 |
Portage will do this with the -n option if you would rather portage did |
100 |
it. Then you can unmerge kde-meta or whatever you use to install KDE 3 |
101 |
and run --depclean -p. I would run with the -p option first since you |
102 |
may see something else you want to keep or some other package that you |
103 |
need to check on before removing. The -a option works to. You can say |
104 |
no if it is not what you want just yet. |
105 |
|
106 |
Dale |
107 |
|
108 |
:-) :-) |