Same here! I ended up having all gems in ./asin, which was painful.. even 'whole project search' in rubymine was finding things there ;)
bundle install should warn about this.. On Jul 30, 9:58 am, Pete <g...@elusivestars.com> wrote: > Thank you so much - this was driving me crazy!!! > bundle path in config was set to rmagick > > BUNDLE_PATH: rmagick > > On Jul 29, 1:17 am, Frederick Cheung <frederick.che...@gmail.com> > wrote: > > > > > > > > > On Jul 29, 9:04 am, Pete <g...@elusivestars.com> wrote: > > > > I am running ruby 1.9.2p290 and Rails 3.0.9 on OSX Lion > > > > When I run bundle install, it installs into rmagick directory and > > > creates subfolders for ruby/1.9.1/gems... > > > > Why is bundle installing gems under 1.9.1/gems ? > > > Well it's installed it into a folder called rmagick because you've > > accidentally told it to do so by doing bundle install rmagick (bundle > > install doesn't allow you to install specific gems, it looks like it > > interprets an argument passed to it as a path. That setting is stored > > in the app's .bundle/config) > > > The hierarchy inside that folder is (I believe) because bundler is > > replicating rubygems layout. It's 1.9.1 rather than 1.9.2 because > > 1.9.1 is the api version number (much like how on 1.8.7, gems would > > have gone in a folder called just 1.8) > > > Fred > > > > Thanks -- 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-talk@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.
