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

[neuewelle@mastodon.social]

@marcoarment I think it's a Linux convention, and even they get confused sometimes https://itsfoss.com/apt-update-vs-upgrade/

[aaronw@hachyderm.io]

@marcoarment My mnemonic (which may or may not work for you) is that “update” comes before “upgrade” alphabetically, so that’s the one you should run first.

[jimmitchell@indieweb.social]

@marcoarment Ditto. I’ve just learned to do the opposite of what my gut tells me to do and nail it every time.

[chrishas35@hachyderm.io]

@marcoarment IIRC upgrade used to not update, now I feel like you can just upgrade and be good. Historicaly it matched Linux package managers

[joschi@hachyderm.io]

@marcoarment You've made a typo in "topgrade".

GitHub - topgrade-rs/topgrade: Upgrade all the things

Upgrade all the things. Contribute to topgrade-rs/topgrade development by creating an account on GitHub.

GitHub (github.com)

[mattwilcox@mstdn.social]

@marcoarment you gotta update the "available software" feed before upgrading to the application versions listed in it.

Might help you remember ... but prob not.

[mlevison@agilealliance.social]

@marcoarment …corked.app pulls a hold my beer on you. I’ve been using Corked unsuccessfully for most of a year. Every time it updates the casks a few of them require I finish from the command line. So really it just exists to yell run a command.

[pfernandes@mastodon.social]

@marcoarment one is a refill the other is another kind of beer?… As long as I don’t have an empty mug I will have them both

[jsnell@zeppelin.flights]

@marcoarment same

[schamschula@mastodon.social]

@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.

[pirijan@c.im]

@marcoarment truly the usb-a of terminal commands

[curtisbridges@mastodon.social]

@marcoarment I just make a single alias that updates everything and then i never have to remember anything but my naming convention.

[dluz@hachyderm.io]

@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.

[anyware@mastodon.social]

@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!

[matt_garber@mastodon.sdf.org]

@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.)

[drdrang@fosstodon.org]

@marcoarment It’s very simple. You use “brew update” when you want to update and “brew upgrade” when you want to upgrade.

[codingitwrong@oldbytes.space]

@curtisbridges @marcoarment yup mine is `brewup`

[malik@mastodon.social]

@marcoarment I‘m not alone

[tomhead@mastodon.social]

@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...

[bbech@mastodon.social]

@marcoarment I never understand why I need to update then upgrade.