I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
-
@marcoarment I think it's a Linux convention, and even they get confused sometimes https://itsfoss.com/apt-update-vs-upgrade/
@NeueWelle @marcoarment Under FreeBSD pkg update downloads the currently available package list, while pkg upgrade downloads and installs the outdated packages. In the MacPorts world that corresponds to port sync and port upgrade outdated.
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment truly the usb-a of terminal commands
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment I just make a single alias that updates everything and then i never have to remember anything but my naming convention.
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment The answer these days is simple! Just run `brew upgrade`, as it auto-updates. Erase `update` from your shell history and never wonder again.
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment This is embarrassingly true! However, about two weeks ago, I had to manually type these many times, and for now (at least), I have it!
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment Thankfully, I suppose, it at least matches the much longer history of Apt syntax behavior on Debian/Ubuntu servers, where you have to *update* the repo lists before being able to *upgrade* any outdated packages.
(And then I also make it easier by aliasing `brew update ; brew upgrade ; brew cleanup` as one run every few days.)
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment It’s very simple. You use “brew update” when you want to update and “brew upgrade” when you want to upgrade.
-
@marcoarment I just make a single alias that updates everything and then i never have to remember anything but my naming convention.
@curtisbridges @marcoarment yup mine is `brewup`
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment I‘m not alone
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment yep, yep, yep
Like `ln -s <source> <target>` or `ln -s <target> <source>`. Which is it? Hope I never end up in a situation where lives depend on getting it right...
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
@marcoarment I never understand why I need to update then upgrade.
-
I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try
-
R relay@relay.an.exchange shared this topic

