The "not installed" language is a bit misleading. I recently reconfigured my computer using my personal bootstrap repo which installs autoupdate, but never runs brew autoupdate --start. Thus, when I tried running brew autoupdate --status, I thought something had gone wrong with the installation (unlikely since I used a Brewfile). The previous message looks like it could be brew itself saying the command is not installed.
After trying brew autoupdate --version I realized what had happened. Since this message can only ever be displayed once the package is installed, using the term "configured" makes more sense, at least to me.
Seems reasonable enough to me. Thank you @emroch, and apologies for the long wait here; getting internet set up properly after moving house a while back proved quite the hassle 🙄.
The "not installed" language is a bit misleading. I recently reconfigured my computer using my personal bootstrap repo which installs autoupdate, but never runs
brew autoupdate --start
. Thus, when I tried runningbrew autoupdate --status
, I thought something had gone wrong with the installation (unlikely since I used a Brewfile). The previous message looks like it could bebrew
itself saying the command is not installed.After trying
brew autoupdate --version
I realized what had happened. Since this message can only ever be displayed once the package is installed, using the term "configured" makes more sense, at least to me.