The question is: is this way of installation correct? Or if not, then what could be the possible problems and what is the best way now to fix everything?
I don’t know that there is necessarily one correct way.
Every Project has its own requirements and therefor its own list of dependencies.
As you’ve noticed, when you tried to fire up a project, it kept asking for missing dependencies. That’s normal for projects with limited documentation, you instead hope but don’t always get a list of dependencies in the project’s README. Also, I don’t know exactly how your projects’ files are distributed, but if they are themselves deployed as part of a package management system (eg you’re working with Ruby on Rails, so you should look for a gem) then that would manage the dependencies automatically for you.
Just beware of one thing I found using Ruby on Rails…
I found that you <must> use the very common bundle install from the openSUSE Ruby repo and not the universal version installable as a gem.
I always use rvm in installing ruby on rails. It allows you to choose what version of ruby you want to use as well as what version of rails you would like to use as well.
That’s OK but working with the openSUSE repos, it’s also as easy as daxh describes, you only need to install the base Ruby package and all the dependencies installed after that will look for that version.
I forgot to mention that there is a really great tutorial on setting up ruby on rails done by onemonthrails I would check it out, it will save you time in the long run.