On Thu, May 22, 2008 at 11:21:15AM -0700, Steve Lamb wrote: > On Thu, May 22, 2008 10:16 am, Sam Leon wrote: > > andy wrote: > > Trying running "aptitude clean" > > "aptitude autoclean" is a better suggestion. Clean removes all cached > deb files. Autoclean removes all old cached deb files while retaining > the most current cached files in case they're needed. Suggesting clean > might remove files they will need while suggesting will leave them with > those files while removing the files they most likely will not need.
While that is accurate as far as it goes... How likely is the average user to ever need the cached debs? Personally, I've been running Debian continuously for nearly a decade (that long already? sheesh...) and I have never had use for a cached deb for anything except: 1) Installing to a second machine without redownloading (although, really, I've been far more likely to just redownload on the second machine) 2) Noticing that I messed up an option during the package install and deciding to uninstall/reinstall rather than fixing the initial install I also seem to recall seeing a thread recently which asked what the cached debs are good for. Nobody suggested anything that didn't fall into those two catgories. Realistically, if you're not going to install to additional machines and it's been more than a day or two since you installed a package (to provide time to notice any install/configuration problems), the odds of needing the deb again are pretty much nil. Using "clean" instead of "autoclean" will be fine in the large majority of cases. -- News aggregation meets world domination. Can you see the fnews? http://seethefnews.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
