HOMEBREW_NO_AUTO_UPDATE=1 still updates? #3394
Unanswered
FreQRiDeR
asked this question in
Everyday usage
Replies: 2 comments
-
The environment variable is called HOMEBREW_NO_AUTO_UPDATE for a reason: it stop automatic And there's no HOMEBREW_NO_AUTO_UPGRADE environment variable, also for a reason: https://docs.brew.sh/FAQ#why-does-brew-upgrade-formula-or-brew-install-formula-also-upgrade-a-bunch-of-other-stuff |
Beta Was this translation helpful? Give feedback.
0 replies
-
Right ;)
… On Jun 28, 2022, at 9:45 PM, Adrian Ho ***@***.***> wrote:
The environment variable is called HOMEBREW_NO_AUTO_UPDATE for a reason: it concerns the effects of brew update.
And there's no HOMEBREW_NO_AUTO_UPGRADE environment variable, also for a reason: https://docs.brew.sh/FAQ#why-does-brew-upgrade-formula-or-brew-install-formula-also-upgrade-a-bunch-of-other-stuff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I entered ‘HOMEBREW_NO_AUTO_UPDATE=1 brew install mplayer’ and brew has been downloading new packages? Python 3.11 etc... It appears to be updating anyways? I have super slow internet and it’s taking forever! Multiple sessions over 3 days! I just want to grab a package! Lol! Granted, I am on Mojave, (unsupported) and it’s an old clone that hasn’t been updated in a long time? Is HOMEBREW_NO_AUTO_UPDATE superseded by incompatible packages/OS or am I doing something wrong? I’m afraid AUTO_UPDATE will break my brew install!
Beta Was this translation helpful? Give feedback.
All reactions