I am using MacOS. I have already bunch of softwares installed in my computer. Recently I have installed Homebrew. Now I want all my softwares (supported by homebrew) to get updated by Homebrew.
How can I migrate those to homebrew without uninstalling and reinstalling those?
I tried to find solution from web but didn't find anything.
Related
MacOS: Ventura 13.1
I have several packages on my Mac installed using Homebrew. I am dealing with a situation, following the update to Ventura 13.1, where the only solution may be to uninstall and re-install Homebrew.
What are my options, if I want to make sure all the tools/apps I installed using Homebrew are re-installed when the process is done?
It should be as simple as:
brew bundle dump
which creates a Brewfile of all your taps and packages, followed by:
brew bundle
which reinstalls everything you had before from the Brewfile.
Using MacOS Monterey, m1 chip.
Installed homebrew and used homebrew to install miniconda.
However, the Miniconda which was downloaded via homebrew did not work. Rather, the miniconda installer works.
Thus, i would like to uninstall the miniconda that was downloaded via homebrew (to avoid any potential conflict) but have difficulties doing so (see screenshot). Please advise how i can safely uninstall the miniconda that was downloaded via homebrew, while keeping the one via installer intact. Note that path in which the miniconda was installed are 2 different paths for each installation method.
I'm trying to install Xdebug on macOS Catalina but home-brew no longer allowed to run as root. Worked fine before Catalina update.
I was running Xdebug under Mojave but Catalina upgrade broke it. Removed extension to reinstall and then hit hombrew issue: get the following error when running brew as root:
Error: Running Homebrew as root is extremely dangerous and no longer supported.
As Homebrew does not drop privileges on installation you would be giving all
build scripts full access to your system.
Brew should be working without using sudo.
If that's not the case, your homebrew install is broken and you might need to reinstall it.
In any case brew doctor is something you can always consult.
After you got your homebrew fixed,
looking into Can't install xdebug on Mac with Homebrew might be of help.
Updating homebrew should do the trick -
brew update
homebrew supports the installation of different versions of a package.
Homebrew install specific version of formula?
But I don't see different versions specified in homebrew formulas.
https://github.com/Homebrew/homebrew-core/blob/master/Formula/bash.rb
Does anybody know how the support of different versions of a package is implemented in homebrew? Thanks.
There is at least three different ways package versions are supported by Homebrew.
1) With brew switch, you can switch back to a version of a package you already installed. For example typing brew switch ansible, I obtain:
ansible installed versions: 2.7.5, 2.7.6
using brew switch ansible 2.7.5, I can switch back to an old version, but this works only for versions that have been already installed.
2) With versioned formulas, you can choose an old version of MySQL with brew install mysql#5.5 or brew install mysql#5.6. This works because there is the corresponding formulas: mysql#5.5.rb and mysql#5.6.rb.
3) You can use the git history to go back to any version of a formula, read this question/answer for details: Install older version of Pandoc (<2) using homebrew
After I installed Homebrew,
Then I try the brew doctor command, there comes warnings:
Could I know the reasons and How to fix it? Could I just ignore these warnings?
The files reported by brew doctor are added by a software (that you manually installed before installing Homebrew) that uses a library for the Tcl/Tk language.
Homebrew also provides a library for Tcl/Tk and the existing files will conflict with those installed by Homebrew if you install a package that requires the Tcl/Tk library.
You don't have to worry for now and, very important, don't try to "fix" anything (especially don't remove files).
What you can do to "fix" it is to find out what program installed those files (it was not installed using the App Store, you installed it manually) and see if Homebrew provides it. If it is a macOS GUI application then Homebrew doesn't provide it (it contains only command line applications, no GUI) but Homebrew Cask might do it.
Use
$ brew search app
or
$ brew cask search app
If you are lucky and you find it and you are pleased with the version provided by Homebrew then you can uninstall the application using the uninstaller it hopefully provides then reinstall it using Homebrew (or Homebrew Cask).
You can run brew doctor between uninstall and reinstall to make sure the uninstaller removed all the files listed in the output of brew doctor now.
As written at the beginning of brew doctor's output, you can safely ignore these warnings if everything you use Homebrew for works fine.