Geek Answers Handbook

Will the gem update -system update rails be updated from 2.3.8 to 3.0?

If I had a second computer, I would just do it and take a look - but I fine-tuned this thing so as not to start 3.0, yet ... I do not want to fuck it. Took the clock and watch to get here. Basnichno - I want the rails to be at 2.3.8 for a while ... so be it

gem update --system

upgrade rails version 2 → 3? I read the documents without a clear answer, and I think it will be so, but maybe I would learn something new. Otherwise, I update each (of 8 - 1) gems that I have. thanks...

+7
ruby rubygems
source share
4 answers

gem update --system updates only RubyGems.

gem update update all installed stones to the latest versions, so it will upgrade Rails to 3.0.0.

Before upgrading gems, you can freeze your app on Rhine 2.3.8 by doing

 rake rails:freeze:gems

in the application folder. Thus, your application will be associated and run in rails 2.3.8, even if you upgrade the global stone to rails 3.

At any time, you can install a specific version of rails through:

 gem install rails -v 2.3.8 (or another version of your choice)

This can potentially install multiple versions of gem at the same time, so you can create and develop an application with any version that suits you.

Or you can install RVM to create and switch between any number of ruby ​​/ rails development environments, for example. Ruby 1.8.7 with Rails 2.3.9 and ruby ​​1.9.2 with Rails 3.0.0, etc.

+23
source share

This command should simply update the RubyGems software, not the gems you installed.

In the help command line:

 → gem help update Usage: gem update GEMNAME [GEMNAME ...] [options] Options: --system Update the RubyGems system software
+2
source share

theIV answered this admirably and correctly, but I found myself in a unique position to answer your question very specifically, so here you go:

C:> gem list --local | find the "rails"

rails (2.3.5)

C:> gem update --system

Update RubyGems Update Update rubygems Successfully installed rubygems-update-1.3.7 Update RubyGems to 1.3.7 Install RubyGems 1.3.7 Installed RubyGems 1.3.7

 === 1.3.7 / 2010-05-13

Note:

http://rubygems.org is now the default source for downloading gems.

You may have sources installed through ~ / .gemrc, so you should replace http://gems.rubyforge.org with http://rubygems.org

http://gems.rubyforge.org will continue to work for the foreseeable future.

New features:

  • gem * gem install and gem fetch commands now report alternative platforms when no match is found. * gem contents --prefix is ​​now the default, as specified in --help. mistake

    27211 Mamoru Tasaka. * gem fetch can extract old versions

    again. Mistake No. 27960 by Eric Hankins.
  • gem query and friends output now lists platforms. Mistake No. 27856 by Greg Tan. * gem server now allows you to specify multiple gem dirs for documentation. Error No. 27573 from Yuki Sonoda. * gem unpack can unpack gems again. Mistake No. 27872 from Timothy Jones. * gem unpack now unpacks removed gems. * --user-install no longer by default. If you really liked it, see Gem :: ConfigFile for how to set it by default. (This change was made in 1.3.6)
  • RubyGems now supports a platform for IronRuby. Patch No. 27951 from Will Green.

Bugs fixed:

  • Require rubygems / custom_require if --disable-gem has been set. Error No. 27700 from Roger Pack.
  • RubyGems now protects against exceptions thrown by plugins.
  • rubygems / builder now requires user_interaction. Ruby error # 1040 from user Phillip Toland.

  • Gem :: Dependency Support # version_requirements = with warning. Fix older versions of Rails. Mistake

    27868 by Wei Jen Lu.

  • Gem :: PackageTask depends on the dir package, as does the other rake package tasks, so dependencies can be properly connected.

RubyGems installed the following executables: C: / languages ​​/ ruby ​​/ bin / stone

Updated RubyGems system software

C:> gem list --local | find the "rails"

rails (2.3.5)

+1
source share

I would recommend you switch your project to using a provider , then you can stop worrying about it. It is easy (and well tested) to do with Rails 2.3.8 and it is designed to solve this problem .

Your best best result is to install RVM and use gemsets . Alternatively you can check rip .

(I know this does not directly answer your question - I am going to post this as a comment, but with the amount of content that I would like to add, my only choice is to give an answer.)

+1
source share

More articles:


All Articles