Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Currently there is installer for Ruby 2. Is it possible that we can also have installer for Ruby 1.
The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. Hello skwong Ruby 1. At the time 1. Sign in to your account. In initial-setup. Probably these three lines:. But this doesn't really work anyway. Sure, 1. But this doesn't automatically make all ruby commands go to 1. To do that, you'll have to use:. But this is still not good enough because 1. Also, even if we don't remove 1. So things break.
Sorry if some of this is unclear. I don't claim to be an expert on any of this stuff, I've just been piecing it together for fun. If anyone has a good understanding of what I'm talking about, please explain it to me The text was updated successfully, but these errors were encountered:. I'll have to find someone who's more knowledgeable on Ruby than me to help me fix any possible issues Sorry, something went wrong.
Also on Digital ocean is the epel repos not installed so yum install facter and hiera fail. I solved this by moving the install of the puppetlabs repo to the intital setup because the packages are in there. You have to install the rdoc-data gem. I found that before I could successfully say rdoc-data --install so as to make the ri data be installed in the right place, I had to restart the computer; perhaps that was overkill, but apparently I needed to make the shell environment straighten itself out, or something.
Elated by this success, I proceeded to download and install Ruby 1. First, before trying to build Ruby 1. Download it, untar it, cd into the folder, and do the usual dance:. A very recent version of RubyGems is already included, so test it by saying gem --version. This was the step that alerted me earlier to the fact that things had gone wrong.
I was so happy about this that I wrote a little note on StackOverflow about it. The version of RubyGems included with Ruby 1. Now we have to deal with TextMate. Everything appears to be just fine — TextMate is using Ruby 1.
Instead of reporting the error message in orderly fashion, we get a horrifying segmentation fault from a script deep inside TextMate. Substitute the contents of the gist for the contents of this script. Presto, Ruby 1. Now I can play with Ruby 1.
0コメント