Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

71%
+3 −0
Q&A How do I safely replace brew on Big Sur?

Since asking this question I've updated to 12.2 (Monterey), but it's the same problem on either. I was nervous about blowing away my existing brew installation, even if I first captured a list of ...

posted 2y ago by Monica Cellio‭

Answer
#1: Initial revision by user avatar Monica Cellio‭ · 2022-05-15T20:01:47Z (almost 2 years ago)
Since asking this question I've updated to 12.2 (Monterey), but it's the same problem on either.

I was nervous about blowing away my existing `brew` installation, even if I first captured a list of packages that I'd need to reinstall.  I found a [blog post](https://blog.smittytone.net/2021/02/07/how-to-migrate-to-native-homebrew-on-an-m1-mac/) about installing the M1 version of `brew` alongside my existing one.  It turns out to be straightforward: the older version installed into `/user/local/bin` while the new one installs into `/opt/homebrew`, so they don't compete with each other.  After updating PATH I can use the new one by default but still have access to the old one if I should need it.  I defined an `oldbrew` alias, in part for the convenience and in part as a reminder to future-me that I still have that lying around.  If, in the future, I go through old-brew's packages and install them all using new-brew, then it'll be safe to remove the old one.  Until then, as far as I can tell, nothing's broken.

(Unfortunately, updating `brew` did not solve the Ruby problem that led me to replace `brew` in the first place.  So this might have been a red herring, but it's probably better to be on the version of `brew` that's designed for my current hardware.)