Rick Denatale wrote: > That's actually not the whole story, and excerpt from the output of > gem help install: > > Description: > The install command installs local or remote gem into a gem > repository. > > For gems with executables ruby installs a wrapper file into the > executable > directory by default. This can be overridden with the --no-wrappers > option. > The wrapper allows you to choose among alternate gem versions using > _version_. > > For example `rake _0.7.3_ --version` will run rake version 0.7.3 if > a newer > version is also installed.
What about if Rails 2.3.5 is installed and then 1.2.5 is installed? It seems like after that rails -v will still give 2.3.5. So the default executable is not overwritten or linked to 1.2.5 but to the newest version. Also, if we run rails _1.2.5_ the won't all the supporting files, script, etc, etc also need to be versioned? So probably that is automatically taken care of as well? So, supposedly, we can install rails in ANY ORDER -- 2.3.5 first, and then 2.2.2 and then 1.2.5 and they still all work well, and the default one is still the 2.3.5 version? wow, if only Windows application can do that too... -- Posted via http://www.ruby-forum.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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
