Hi, I'm Gregory Brown.
My goal is to help software developers get better at what they do, whether they've been at it for five weeks or fifty years.
(he/him)
Lately I have been anxious whenever I install a new version of Ruby using ruby-install because it seems to then do a homebrew update of various dependencies, which in turn often breaks various other things (this most recent time, openssl and postgresql)
I am 95% sure I am "doing it wrong" in some way and that I could avoid these issues if I dug into them, but the problem impacts me rarely enough that it hasn't risen to the level of "need to fix it" yet.
More broadly, any time that there is a combination of the following factors, I am in for a worrisome time:
I don't understand the tool well
The tool has a potential to do (not easily reversible) damage
Solutions to any problems caused by tool are not easy to find and/or I do not immediately understand the solutions and apply them blindly.
I do not use the tool often, but I also don't have an easy obvious alternative to use which avoids the other risk factors listed above.
As a general rule I really, really, really prefer to understand the tools I use and their potential impact before using them. But because this isn't practical to apply to everything, all the time there are always some things that slip through the cracks from time to time.
Lately I have been anxious whenever I install a new version of Ruby using ruby-install because it seems to then do a homebrew update of various dependencies, which in turn often breaks various other things (this most recent time, openssl and postgresql)
I am 95% sure I am "doing it wrong" in some way and that I could avoid these issues if I dug into them, but the problem impacts me rarely enough that it hasn't risen to the level of "need to fix it" yet.
More broadly, any time that there is a combination of the following factors, I am in for a worrisome time:
As a general rule I really, really, really prefer to understand the tools I use and their potential impact before using them. But because this isn't practical to apply to everything, all the time there are always some things that slip through the cracks from time to time.
You may try
rbenv, which does not use brew whatsoever.