1 |
Grant wrote: |
2 |
> > > I think you're right about that. Can I configure eclean to wait a |
3 |
> > > certain number of days since a package was removed before cleaning it? |
4 |
> > > Even if I only run it once per week, it could remove a package that |
5 |
> > > was updated yesterday that I find out I need tomorrow. |
6 |
> > > |
7 |
> > > - Grant |
8 |
> > |
9 |
> > |
10 |
> > -t, --time-limit=<time> don't delete files modified since <time> |
11 |
> > <time> is an amount of time: "1y" is "one year", "2w" is "two |
12 |
> weeks", etc. |
13 |
> > Units are: y (years), m (months), w (weeks), d (days) and h (hours). |
14 |
> |
15 |
> Thanks Dale. |
16 |
> |
17 |
> > I found that in man eclean. |
18 |
> |
19 |
> I'm sorry, I didn't consider a parameter like that for some reason. |
20 |
|
21 |
It actually has quite a few options. I rarely use them on my new rig |
22 |
but did on my old rig. My old rig is MUCH slower than this new one. |
23 |
|
24 |
> |
25 |
> Should it be alright to depclean every day? As long as I use |
26 |
> --time-limit with 'eclean packages', I should be able to reinstall |
27 |
> anything that depclean removes even if it's pruned from Portage. |
28 |
> |
29 |
> - Grant |
30 |
|
31 |
I run depclean about once a month after a large update, usually KDE, qt |
32 |
or something like that. I sync and update about twice a week. I try to |
33 |
time mine to hit those important updates to things like KDE or |
34 |
something. I'm actually waiting on KDE 4.9.4 to hit the tree now. It |
35 |
should be there pretty soon, if there is no major problems. |
36 |
|
37 |
I would set a rough update time schedule. If say you set yours to update |
38 |
every week, then keep two maybe three weeks of old packages. If a |
39 |
package can work for a few weeks, survive reboots and a couple updates, |
40 |
then odds are it is safe to remove the binaries you built for it. The |
41 |
sources, I usually only keep what I have installed. Most of the time |
42 |
that is enough. If you have the hard drive space, you can keep them |
43 |
like you do the binary package. If you pick a monthly update time |
44 |
frame, then adjust your time frame for old packages. You may can keep |
45 |
less of them depending on how you run your rig. |
46 |
|
47 |
When you use eclean and friends with no options, it seems to leave a |
48 |
pretty good set of binaries behind. It leaves what is installed plus a |
49 |
older version or two. It's been a while since i really looked into this |
50 |
but it seems to have a fairly safe setting when you just run the plain |
51 |
command with no options. When you use the -d option, it leaves only |
52 |
what you have installed and gets rid of everything else. The -d option |
53 |
is about the most aggressive option for eclean. |
54 |
|
55 |
This is just to give you ideas. This is one of those 'it depends' |
56 |
questions. The technically correct way is to run depclean after each |
57 |
full update. Thing is, I doubt it will hurt anything if you leave them |
58 |
on there except for taking up drive space. |
59 |
|
60 |
Just don't forget to update the configs after each update. Sometimes |
61 |
missing those can lead to a system that won't boot. It's not very |
62 |
likely but they do happen from time to time. |
63 |
|
64 |
Another thing about my system that may help you, I keep a copy of /etc |
65 |
and my world file backed up. When I reboot, which is not to often, I |
66 |
make a new backup of /etc. Right now, my uptime is almost 75 days. I |
67 |
keep that backup just in case something will only break when rebooting. |
68 |
Some config files are only read when booting so until you reboot, you |
69 |
don't know you have a problem. Having a copy of the world file is good |
70 |
in case you lose the drive with the OS on it. You can at least know |
71 |
what you need to emerge to get back to where you were. |
72 |
|
73 |
Hope that helps. |
74 |
|
75 |
Dale |
76 |
|
77 |
:-) :-) |
78 |
|
79 |
-- |
80 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |