Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
With git is possible to jump back to early versions of a project.
Now, to work with these early versions, they depend often on old versions of libraries. Is it possible to circumvent problems like these:
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:220:in `specification': can't activate haml (= 2.1.0, runtime), already activated haml-3.0.18 (Gem::Exception)
You can specify a version number with each of your gem requirements, either in your gemfile (Rails 3) or your environment files (Rails 2). As long as you don’t uninstall any of the versions you’re using, you should be able to switch back and forth as you please.