On Wed, Jul 27, 2011 at 12:24 AM, Rhett Sutphin <rh...@detailedbalance.net>wrote:
> > I am looking at upgrading buildrs dependency on rubygems to a later > version > > and being more explicit about the version. i.e. Something like > > > > spec.add_dependency 'rubygems-update', '>= 1.8.6' > > Good idea, though the gemspec line you want is something like this: > > s.required_rubygems_version = ">= 1.8.6" > oops - thanks! > Is 1.8.6 specifically required? I would ask that you try to make this as > loose as possible. Many releases in the 1.7 and 1.8 line have been broken or > unreasonably noisy, so I have been conservative about upgrading. (I'm still > mostly using 1.6.2.) > 1.6.2 was log enough ago that it does include all the deprecation warnings that I am wanting to fix. I tried playing around witha few versions in between but as you say many of them seemed buggy. 1.8.0 and 1.8.1 in particular seemed more bad than usual but 1.8.3 and 1.8.4 did not seem much better. Havig at the release timing of each version @ http://rubygems.org/gems/rubygems-update/versions would seem to support that idea. So far I have yet to find any bugs i 1.8.6 but I am doing some more comprehensive testing over the next week or so. So unless any bugs pop up I would prefer to keep it at 1.8.6 and if not roll back to 1.8.5. Thoughts? -- Cheers, Peter Donald
