Regain Disk Space from Homebrew

By  on  

One of my favorite utilities is Homebrew, the shell utility for installing and upgrading other utilities -- it's a lazy developer's dream.  Dreams can easily turn to nightmares, however, and I recently learned that Homebrew caches older versions of installed packages, leading to loads of disk space being used up by old files.

Want all of that disk space back?  Run brew cleanup -s:

Homebrew cleanup

I understand why Homebrew keeps the previous versions around but when utilities are stable, it's really time to take back the bytes.  My first run of brew cleanup -s recovered 640MB of disk space, which is peanuts relative to the size of modern hard drives, but it's space that I want back!

Recent Features

Incredible Demos

  • By
    Select Dropdowns, MooTools, and CSS Print

    I know I've harped on this over and over again but it's important to enhance pages for print. You can do some things using simple CSS but today's post features MooTools and jQuery. We'll be taking the options of a SELECT element and generating...

  • By
    Image Data URIs with PHP

    If you troll page markup like me, you've no doubt seen the use of data URI's within image src attributes. Instead of providing a traditional address to the image, the image file data is base64-encoded and stuffed within the src attribute. Doing so saves...

Discussion

  1. Nelson Rocha

    Just dropping a huge thank you for sharing this!

    ==> This operation has freed approximately 6.9GB of disk space.
    
  2. gn0st1c

    another thank you.. just saved ~2gb.

    ==> This operation has freed approximately 1.9GB of disk space.

  3. dorian logan

    df -==> This operation has freed approximately 562.3MB of disk space.

  4. I got about 32.2GB back on my laptop, which out of a 250GB drive is a chunk of space worth having. That also might explain why my Time Machine backups were always much bigger than I was expecting. Thanks for the tip. One question: I didn’t include the “-s” parameter – what does that do?

    • Andres

      mauvedeity : scrub the cache, I guess

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!