Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Typing <code>gem env</code> (Using your old Ruby install's gem command) at a command prompt gives something similar to:</p> <pre><code>&gt; RubyGems Environment: &gt; - RUBYGEMS VERSION: 1.3.6 &gt; - RUBY VERSION: 1.9.1 (2009-07-16 patchlevel 243) [i386-mingw32] &gt; - INSTALLATION DIRECTORY: C:/Ruby19/lib/ruby/gems/1.9.1 &gt; - RUBY EXECUTABLE: C:/Ruby19/bin/ruby.exe &gt; - EXECUTABLE DIRECTORY: C:/Ruby19/bin &gt; - RUBYGEMS PLATFORMS: &gt; - ruby &gt; - x86-mingw32 &gt; - GEM PATHS: &gt; - C:/Ruby19/lib/ruby/gems/1.9.1 &gt; - C:/Users/Username/.gem/ruby/1.9.1 &gt; - GEM CONFIGURATION: &gt; - :update_sources =&gt; true &gt; - :verbose =&gt; true &gt; - :benchmark =&gt; false &gt; - :backtrace =&gt; false &gt; - :bulk_threshold =&gt; 1000 &gt; - REMOTE SOURCES: &gt; - http://rubygems.org/ </code></pre> <p>(On Windows... I imagine Snow Leopard will have a similar format)</p> <p>The GEM PATHS field is the interesting thing here. If you go to those directories listed, you should see a folder named <strong>cache</strong>. That will contain a list of .gem files corresponding to all the installed gems in that specific directory. You should just be able to call <code>gem install *gemname*</code> on each of those gem files (using your <em>new</em> Ruby install's gem command).</p> <p>EDIT: Mistakenly referred to INSTALLATION DIRECTORY instead of GEM PATHS. Greg reminded me that there are multiple locations known by a specific installation of Rubygems. All of those locations needs to be checked for gems used by that installation of Ruby.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhere are the GEMs when Ruby compiled manually in Mac OS X 10.6.8?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjason.rickman
    1. USjason.rickman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm not sure of Rubygem's behavior for dependencies when installing from a local .gem file. You might want to include the --ignore-dependencies flag to avoid pulling dependencies from a remote source (since presumably you already have all necessary dependencies locally).
      singulars
      1. PO
      1. USjason.rickman
    2. COWindows Gem configuration is not the same as Snow Leopard, because Apple configures the default locations, and want their own gems, plus the user gems, plus user `sudo` gems. Microsoft doesn't include Ruby so it's the Ruby installer for Windows that determines the locations.
      singulars
      1. PO
      1. USthe Tin Man
    3. CO@Greg : Regardless of who determines the install locations, doesn't Rubygems know where that location is? Apologies if I'm outside my realm of knowledge here; I assumed Rubygems would work the same on all supported OSs.
      singulars
      1. PO
      1. USjason.rickman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload