#15 Provide a way to specify gem processing order - GemInstaller

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#15 ✓resolved

Provide a way to specify gem processing order

Reported by Chad Woolley | October 13th, 2008 @ 10:31 PM | in 1.0 Release

Otherwise, you can have dependency issues, such as using mislav-will_paginate and rails 2.0.2 with rails > 2.0.2 installed.

See this app to reproduce the error:

http://github.com/jtrupiano/gemi...

Solution is probably to preserve order of gems, but this is trickier with multiple config files merged. See config_builder.rb.

Workaround is to explicitly activate proper version of rails before invoking autogem:

require 'rubygems'
gem 'geminstaller', ">= 0.4.5"
require 'geminstaller'
gem 'rails', '= 2.0.2'
GemInstaller.autogem('--exceptions')

Comments and changes to this ticket

Chad Woolley October 29th, 2008 @ 06:04 PM
The (arguable) root cause of this bug is reported here:

http://sod.lighthouseapp.com/pro...

Although there should still be a way to specify gem processing order.
Chad Woolley February 3rd, 2009 @ 05:41 PM
- State changed from “new” to “resolved”
Fixed in release 0.5.0.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.