> > > 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?
This just got me today. I recently updated google-chrome on one system, 'eclean packages' ran at some point, then chrome started acting up and I couldn't go back to the previous version because eclean had wiped out the package. I don't think we can count on --time-limit to save us because it can still wipe out all previous versions of a package. What we need is a way to keep at least one older version of each package. - Grant
