Way to Uninstall Packages with Homebrew: Guide

Homebrew packagesWhether you have ever installed Homebrew on a Mac in order to use it as a package manager for different Unix & command-line utilities. You may have installed a handful of packages considered advantageous to you. But what whether you no longer need/have one. So you like to remove specific Homebrew packages?

Well, guys! it turns out that removing packages/formula with Homebrew is pretty straightforward. And also uninstalling & removing the just packages from the Homebrew is just as simple as installing them in the first place.

In order to remove, we are not talking just about uninstalling the Homebrew itself, we are just talking about clearing the specific packages just from the Homebrew.

Uninstall and Remove Homebrew Packages

The appropriate way in order to remove a Homebrew package is just with the uninstall or also delete the command.

Though the uninstall Homebrew package command simply seems like this:

brew uninstall packageName

However, guys the uninstall Homebrew package command looks like this:

brew remove packageName

As you probably have predicted by now, so the clear-out & uninstall commands are also similar. And get the exact result; the removal of the Homebrew package.

For instance, in order to remove & uninstall Telnet (presuming you installed telnet on the Mac simply with the Homebrew anyway). So then you would use the below-mentioned command string:

brew uninstall telnet

Or you are also able to use the uninstall command for a similar effect:

brew remove telnet

Clearing a package just from the Homebrew is quick. As there is no need in order to download anything. So it only removes the Homebrew package just from the Mac.

You are also able to make sure the package was cleared by trying. In order to manage the command again. Or simply by checking where the Homebrew packages are also installed. And you guys will also find the package you cleared is no longer there.

Read this article: iCloud Full Site: Login to iCloud from iPhone/iPad/iPod touch

Additional Homebrew Package Uninstall Options

Two flags are also there that you are able to also pass to the Homebrew remove the command too; –force & –ignore-dependencies.

However, the –force flag (or -f) will forcibly clear the package just along with removing all the versions of that package/formula.

Similarly, the –ignore-dependencies flag performs just what it sounds just as. Similarly, it will disregard dependencies for the formula in the query when removing the designated package.

To Manage the Dependencies when Removing the Homebrew Packages

However, just one thing to be mindful of when deleting & uninstalling packages from Homebrew is that whether the package being removed has dependencies. Though that are in use by another package or formula, so then that probably break it originating the secondary package just to no longer work in a right way. Probably the easiest way in order to stop that is to use the optional –ignore-dependencies flag. For instance:

brew uninstall --ignore-dependencies telnet

Whether you are not confirming that what dependencies remain with a specific Homebrew package. You are also able to use the deps command in order to find that out:

brew deps packageName

For instance, whether you guys install python3 on the Mac by using the Homebrew approach. That also has a fair amount of dependencies, managing that command would look something just like the following:

% brew deps python3
gdbm
openssl
readline
sqlite
xz

After all guys, lots of other packages also use those dependencies. Whether you were to uninstall python3 you would nearly certainly like to issue the –ignore-dependencies flag. However, the same applies just to node.js and npm. And many further famous Homebrew packages.

Also read: Way to Record Video on Mac with Webcam and QuickTime

Conclusion

Alright, guys! Do you know of any other procedures or tips related to removing the Homebrew packages & formula? So guys share with us in the comments section below!

Leave a Reply

Your email address will not be published. Required fields are marked *