| 1 |
> > I think you're right about that. Can I configure eclean to wait a |
| 2 |
> > certain number of days since a package was removed before cleaning it? |
| 3 |
> > Even if I only run it once per week, it could remove a package that |
| 4 |
> > was updated yesterday that I find out I need tomorrow. |
| 5 |
> > |
| 6 |
> > - Grant |
| 7 |
> |
| 8 |
> |
| 9 |
> -t, --time-limit=<time> don't delete files modified since <time> |
| 10 |
> <time> is an amount of time: "1y" is "one year", "2w" is "two weeks", etc. |
| 11 |
> Units are: y (years), m (months), w (weeks), d (days) and h (hours). |
| 12 |
|
| 13 |
I just realized that --time-limit doesn't look like it takes into |
| 14 |
consideration when a package was removed from the system, only when it was |
| 15 |
installed. Does anyone know how eclean behaves as far as leaving packages |
| 16 |
behind for a while in case they're needed? |
| 17 |
|
| 18 |
- Grant |
Archives