1 |
> I run depclean about once a month after a large update, usually KDE, qt |
2 |
> or something like that. I sync and update about twice a week. I try to |
3 |
> time mine to hit those important updates to things like KDE or |
4 |
> something. I'm actually waiting on KDE 4.9.4 to hit the tree now. It |
5 |
> should be there pretty soon, if there is no major problems. |
6 |
> |
7 |
> I would set a rough update time schedule. If say you set yours to update |
8 |
> every week, then keep two maybe three weeks of old packages. If a |
9 |
> package can work for a few weeks, survive reboots and a couple updates, |
10 |
> then odds are it is safe to remove the binaries you built for it. The |
11 |
> sources, I usually only keep what I have installed. Most of the time |
12 |
> that is enough. If you have the hard drive space, you can keep them |
13 |
> like you do the binary package. If you pick a monthly update time |
14 |
> frame, then adjust your time frame for old packages. You may can keep |
15 |
> less of them depending on how you run your rig. |
16 |
> |
17 |
> When you use eclean and friends with no options, it seems to leave a |
18 |
> pretty good set of binaries behind. It leaves what is installed plus a |
19 |
> older version or two. It's been a while since i really looked into this |
20 |
> but it seems to have a fairly safe setting when you just run the plain |
21 |
> command with no options. When you use the -d option, it leaves only |
22 |
> what you have installed and gets rid of everything else. The -d option |
23 |
> is about the most aggressive option for eclean. |
24 |
> |
25 |
> This is just to give you ideas. This is one of those 'it depends' |
26 |
> questions. The technically correct way is to run depclean after each |
27 |
> full update. Thing is, I doubt it will hurt anything if you leave them |
28 |
> on there except for taking up drive space. |
29 |
> |
30 |
> Just don't forget to update the configs after each update. Sometimes |
31 |
> missing those can lead to a system that won't boot. It's not very |
32 |
> likely but they do happen from time to time. |
33 |
> |
34 |
> Another thing about my system that may help you, I keep a copy of /etc |
35 |
> and my world file backed up. When I reboot, which is not to often, I |
36 |
> make a new backup of /etc. Right now, my uptime is almost 75 days. I |
37 |
> keep that backup just in case something will only break when rebooting. |
38 |
> Some config files are only read when booting so until you reboot, you |
39 |
> don't know you have a problem. Having a copy of the world file is good |
40 |
> in case you lose the drive with the OS on it. You can at least know |
41 |
> what you need to emerge to get back to where you were. |
42 |
> |
43 |
> Hope that helps. |
44 |
> |
45 |
> Dale |
46 |
|
47 |
Thanks Dale. |
48 |
|
49 |
- Grant |