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
    Full Width Textareas

    Working with textarea widths can be painful if you want the textarea to span 100% width.  Why painful?  Because if the textarea's containing element has padding, your "width:100%" textarea will likely stretch outside of the parent container -- a frustrating prospect to say the least.  Luckily...

  • By
    Drag and Drop Z-Index Stacking

    In an example for a previous post, I showed you how to use opacity during a drag'n'drop transaction. One bit I didn't account for was element stacking and bringing the most recent element to the top of the stack. To do...

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!