Grant wrote: > > > I think you're right about that. Can I configure eclean to wait a > > > certain number of days since a package was removed before cleaning it? > > > Even if I only run it once per week, it could remove a package that > > > was updated yesterday that I find out I need tomorrow. > > > > > > - Grant > > > > > > -t, --time-limit=<time> don't delete files modified since <time> > > <time> is an amount of time: "1y" is "one year", "2w" is "two > weeks", etc. > > Units are: y (years), m (months), w (weeks), d (days) and h (hours). > > I just realized that --time-limit doesn't look like it takes into > consideration when a package was removed from the system, only when it > was installed. Does anyone know how eclean behaves as far as leaving > packages behind for a while in case they're needed? > > - Grant
It's been a while but it used to keep the packages as long as they are in the tree when using the default setting, in other words, no option is given. To me, that can be a really long time for some packages. When I say 'they', I mean a ebuild exists for that version. As I said, that was a while ago but I don't recall seeing anything that it has changed either. If that is wrong, someone please correct. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
