From b38a80323f9cef4415c110b0b05016f98613e870 Mon Sep 17 00:00:00 2001 From: Karel Minarik Date: Fri, 10 Oct 2008 11:41:30 +0200 Subject: Stated the need to specify "config.gem" +:lib+ option for libraries where the Gem name (eg. "sqlite3-ruby") differs from the file itself (eg. "sqlite3") This affects great number of popular gems and is *really* frustrating to get "you have to rake gems:install" permanently when you *know* you just did that. See eg. http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/afefb09908f36db/ --- railties/environments/environment.rb | 2 ++ 1 file changed, 2 insertions(+) (limited to 'railties/environments') diff --git a/railties/environments/environment.rb b/railties/environments/environment.rb index abdb863130..09471f16bc 100644 --- a/railties/environments/environment.rb +++ b/railties/environments/environment.rb @@ -22,8 +22,10 @@ Rails::Initializer.run do |config| # Specify gems that this application depends on. # They can then be installed with "rake gems:install" on new installations. + # You HAVE to specify the :lib option for libraries, where the Gem name (sqlite3-ruby) differs from the file itself (_sqlite3_) # config.gem "bj" # config.gem "hpricot", :version => '0.6', :source => "http://code.whytheluckystiff.net" + # config.gem "sqlite3-ruby", :lib => "sqlite3" # config.gem "aws-s3", :lib => "aws/s3" # Only load the plugins named here, in the order given. By default, all plugins -- cgit v1.2.3