Installed: dev-ruby/bundler-1.2.5 dev-ruby/rubygems-2.0.3 When running "bundle", it returns: Bundler is not compatible with Rubygems 2.0. Please upgrade to Bundler 1.3 or higher. This means all <dev-ruby/bundler-1.3.0 ebuilds should depend on <dev-ruby/rubygems-2.0
It also means that all rails websites are hosed =)
(In reply to Elias Probst from comment #0) > This means all <dev-ruby/bundler-1.3.0 ebuilds should depend on > <dev-ruby/rubygems-2.0 I've removed the old ones, and filed a stable bug for bundler 1.3.5. I've also added a <rubygems-2 dependency to bundler 1.2.x.
(In reply to Michael Orlitzky from comment #1) > It also means that all rails websites are hosed =) Only if you actually use bundler with rails. I don't :-)
(In reply to Hans de Graaff from comment #3) > (In reply to Michael Orlitzky from comment #1) > > It also means that all rails websites are hosed =) > > Only if you actually use bundler with rails. I don't :-) I'm not using it for dependency management, but we run our sites under passenger (with Apache). Passenger uses bundler to perform a sanity check on the installed deps before it will launch the site, so when bundler breaks passenger does too unfortunately. I would much rather it STFU and attempt to launch the site anyway -- that way I could declare my sites' dependencies through ebuilds and not Gemfiles. Is there a better way?
There is a better way! http://michael.orlitzky.com/articles/decoupling_rails_and_passenger_from_bundler.php Although as mentioned it's probably not worth the trouble for pre-packaged apps like Redmine.
(In reply to Michael Orlitzky from comment #5) > There is a better way! We're doing something similar at work, but with Isolate so the mac folks can still pull in the right dependencies automatically. At least Isolate doesn't generate the dreaded Gemfile.lock file, causing issues when system gems are being updated.
