I'm always so confused by the nomenclature in homebrew. Even beyond all the beer terminology, I'm still not sure what the difference between update and upgrade is. The docs simply defines upgrade in terms of itself: "Upgrade everything with:
brew upgrade". Does "everything" include homebrew itself (which is what homebrew update is supposed to do) ? If so are the commands redundant? It just seems like an example of a great tool overall that has all these unnecessary complications.
The brew postgresql-upgrade-database command is a fantastic idea. It's not a huge deal to upgrade by hand, but enough of a hassle that I tend to fall behind.
Has anyone tried to use nix package manager and nix-darwin (<a href="https://github.com/LnL7/nix-darwin" rel="nofollow">https://github.com/LnL7/nix-darwin</a>) instead of brew?<p>I am curious if there is any upside to using it over the hard work brew team is doing.
> We will maintain python2, python3 and python@3 aliases.<p>Is the python3 alias likely to be present indefinitely?<p>I work with beginners a lot, so I look for a simple installation with as few steps as possible. I like that someone who hasn't set up their mac for development can run 'brew install python3', and then use the python3 command to work with the latest version. They don't have to modify their PATH to get started, and as long as they use python3 to run programs and configure a text editor, they don't have to think much about the difference between their Python 3 installation and the system Python.<p>I understand that 'brew install python' will now install Python 3, which is great. But that does mean you have to modify your PATH to have the python command use the homebrew-installed Python 3 interpreter, right?<p>Is it reasonable to continue to recommend that beginners use the 'brew install python3' command?
Homebrew is great, only thing that bugs me is auto update executed before each command, kind of slows down user experience.<p>upd: to disable auto update<p><pre><code> export HOMEBREW_NO_AUTO_UPDATE=1</code></pre>
"On 1st March 2018 the python formula will be upgraded to Python 3.x and a python@2 formula will be added for installing Python 2.7"<p>As someone who really likes Python 3, this makes me really happy
As a PHP developer, merging the PHP repository into core will be disastrous for me. I have 27 packages installed for PHP 5.5 - 7.2, and the versioned extensions will evaporate. So much of my tooling is built around homebrew and the `homebrew/php` tap, that my entire toolchain for development will change.<p>The last time, Apache was switched from installing/running at the system level to user-based. That broke almost everything on my system for a day while I tried to fix it. Worse, there wasn't a warning prompt before the package upgraded.<p>I don't have time for things to break down every 6-12 months.
If I could make one request, it would be that Python formulas get a "python-" prefix, PHP formulas get a "php-" prefix, and so on.<p>There are still some things I don't love about Homebrew but there is quite a lot that I do love. Thank you for continuing to build great software and maintain a high standard for packaging. The binary "bottles" are especially appreciated.
It's slightly unclear to me what will happen for the php formula's, we have several people working very happily with it, easy to switch between major versions and include extensions.<p>> By 31st March 2018 we will deprecate and archive the Homebrew/php tap. Unfortunately we have been unable to maintain an acceptable, consistent user or contributor experience and CI workload through non-core formula taps in the Homebrew organisation so we are continuing to migrate widely used formulae into Homebrew/core and encourage more niche formulae and options to be supported outside the Homebrew organisation.
One thing that I don't know if it's possible with homebrew is installing previous versions of packages. For instance, <i>brew install python3</i> installs python 3.6. How can I install python3.5?