On Sep 29, 2011, at 1:16 PM, Barney wrote:
Hi All,
In trying to port a working version from one computer to another
I had installed the requisites and copied over the files in the rails
project. However one method wouldn't work and it was because the gem
involved wouldn't work with the newest rails. After uninstalling
rails, reinstalling an earlier version and playing with DevKit, et.
al., I've managed to fubar the project so that now it even claims it
can't find rubygems. So I'm inclined to uninstall gems, the devkit
and rails and then copy over the code again, essentially starting
over.
Question 1) what is the proper method of uninstalling those 3?
Question 2) What is the function of the file "Gemfile.lock". Should
it be copied over or will it be generated?
Thanks,
Barney
Let me answer your 2nd question first. The Gemfile.lock specifies the
versions of each gem that were selected to satisfy the dependency
graph. You should copy it over (actually, you should check it into the
repository; you are using a code repository, right?) and then a bundle
install will use those versions. Without Gemfile.lock, it builds a
new dependency graph, either with gems it finds or gems that it
installs, and constructs a new Gemfile.lock with the results.
You can also run `bundle package` to put all the .gem files into
vendor/cache/ (by default) which can also be kept in the repository.
Copy the Gemfile.lock over and see if `bundle install` doesn't just
solve your problem.
-Rob
Rob Biedenharn
[email protected] http://AgileConsultingLLC.com/
[email protected] http://GaslightSoftware.com/
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
