I usually update my Mac’s Hugo Extended version through a shell script that looks for the appropriately named .tar.gz file — e.g., for 0.152.2, that was:
hugo_extended_0.152.2_darwin-universal.tar.gz
… but I see that, starting with 0.153.0, there instead is an actual .pkg file for normal macOS-style installation, apparently due to the resolution of GH Issue #14135. Since Hugo is still a CLI app rather than GUI-based with (e.g.) a “Check for Updates” menu item, what is a Best Practices way for us macOS users to handle version updates going forward? (My GitHub Action for building my site won’t be affected because it’s still calling the Linux version.)
People have been asking for a signed and notarised MacOS for a long time, and since Apple has tighened the security on this (you need to manually go into the security prefs and whitelist any non-signed/notarised app, I decided it was time to do it right, and that meant either pkg or dmg, and pkg is much nicer. And I decided I didn’t want to build a double set.
Also, getting this signing/notariser thing set up was a project on its own. Jeez.
Oh, please don’t misunderstand, @bep — I think it’s a great idea. I’m mainly just trying to figure out how I update it locally going forward. (My old method deleted the previous version and pulled the current one, using an xattr -dr com.apple.quarantine command as a workaround for just the issues you mentioned.)
As for what @ZhenShuo2021 mentioned about hvm, it appears not to have been updated since a couple of months ago, so am I correct in assuming that it wouldn’t yet “know” this .pkg version of the binary? (Perhaps that’s a question for @jmooring.)