drop --no-update-sources switch in the install routine
Reported by Josh Goebel | May 24th, 2008 @ 11:42 PM
It breaks older versions of rubygems and I can't see why it is required... I hacked it out of all the Rakefiles and my install built and installed just fine.
Well apart from the fact I had to install a lot of dependencies by hand, which I think would be the case with or without the new rubygems, right?
Perhaps we should test what version of rubygems they have installed and if it is an older version then not pass that option.
There are still a lot of gems (in my experience) that break with rubygems 1.1 do to the whole require_gem issue... I've had to patch many a rails app to include local, hacked versions of broken gems to support the upgrade of a server to newer rubygems... it's just a pain in the ass if It doesn't have to happen.
Comments and changes to this ticket
-
Jonathan Stott (namelessjon) November 30th, 2008 @ 07:45 AM
- Assigned user cleared.
- Tag set to “bug, suggestion”
- State changed from “new” to “invalid”
I think we now use a lot of other more advanced rubygems functionality.
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.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Rick