When done with #2, I would like to automatically diagnose my entire Ruby environment with a comprehensive system test. Maybe the latter has less of "I'm a developer and I do not write portable code across version platforms / I'm a programming-language/platform designer that cares less about cross-version compatibility." This is a new world for us.) Granted, we tend to do more system programming in C/C++/Python kind of things, and less web-specific stuff like JavaScript/Ruby things. We're guessing this may be driven by the Ruby world may not try to enforce as much cross-Ruby-version compatibility, but we only speculate. I'm used to, as a long-standing swdev manager, managing versions of the software my teams are developing. (I'm not familiar with the term "version manager" to describe the actual version of interpreter/compiler software. Why do we need something to manage versions of Ruby, when we only want one? Is there some reason why we need multiple versions of Ruby? And do we have to separate Ruby "things" separate from a Ruby "version manager"? Is there a "Install Ruby for non-Ruby-developer dummies" resource to help guide us through this? What exactly we're installing and why we're installing it is unclear. So please consider all the historical Ruby-isms that might have been installed for the entire history or Ruby, because chances are I've been installing them since the very early days of Ruby, and I/we still have the same macOS image we've been carrying forward (across upgraded MacBook hardware).Īnd it seems to make most sense to make sure this stuff is all gone (or at least moved out of a functional path) to ensure we have a clean slate to.
Hombrew-based, rbenv, and rvm, and any other Ruby thing/version_manager/intstalled_directory (there seems to be lots of different procedures and no one "standard install procedure-which is all confusing to us).
I want to completely remove every little Ruby file found on the system (besides the -based default Ruby stuff that comes with macOS-I do not to remove or even use that stuff, ever, if I can avoid it). As such, we're simply users and are not invested in learning all the ins-and-outs of Ruby other than just trying to get apps (like Asciidoctor) to run without problems, and that's it.
bash_profile edits, etc.Įven though we (my team) are not Ruby developers, we're running several Ruby-based apps like Asciidoctor. I'm seeking the entire procedure, for everything Ruby-environment related: Ruby "engine," version managers. How do I remove (all old Ruby things), reinstall (preferably one and only one Ruby version), and test my entire Ruby environment (versionmgrs, gems, however this works) on my macOS 10.14.6 system using the "Ruby-community preferred" method (some install/version manager or similar vehicle)?
0 kommentar(er)
