| 1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
| 2 |
> On Fri, 26 Feb 2010 06:34:18 -0800 (PST), BRM wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Aside from that, I'm not sure I have ever really run "emerge |
| 6 |
>> --depclean", but I also rarely uninstall anything, but don't install |
| 7 |
>> things left or right to try out either, so typically upgrades are all I |
| 8 |
>> need to do. |
| 9 |
>> |
| 10 |
> You should still run --depclean as dependencies change and you could still |
| 11 |
> have plenty of no longer needed ones installed. |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
This is very true. I would say that 90% or so of the things --depclean |
| 16 |
removes are not related to packages I removed but what has been moved to |
| 17 |
another package or otherwise satisfied. Lately, there are several |
| 18 |
packages that have had parts move somewhere else. Then the old package |
| 19 |
is no longer needed and should be removed. After all, if it doesn't |
| 20 |
depend on something in the world file, it will never be updated again. |
| 21 |
It's just sitting there doing nothing but taking up space. |
| 22 |
|
| 23 |
Wasn't there a thread a year or so ago that listed the commands that |
| 24 |
should be run from time to time to keep portage healthy? I seem to |
| 25 |
recall one but it was a while back, maybe a year or more. |
| 26 |
|
| 27 |
Now to go do my sync and check to see what needs updating. |
| 28 |
|
| 29 |
Dale |
| 30 |
|
| 31 |
:-) :-) |
Archives