If it's preferable, can someone take a look at all my proposed rubygem packages? Although I managed to get most of them to build using the developer's testing methods. If it's easy to switch them to use RSpec 2.x, by just adjusting dependency and using rspec instead of rake for test validation I can switch all of mine.
Otherwise, I'm not sure how to proceed. ----- Original Message ----- From: Shawn Starr <[email protected]> To: Ruby SIG mailing list <[email protected]> Cc: Sent: Wednesday, July 27, 2011 11:24:34 AM Subject: Re: Migration from RSpec 1.3 to RSpec 2.x then I am getting conflicting views since OpenNebula folks said they asked upstream and they were told to use data_mapper? if anything we would just patch OpenNebula to use 'datamapper' if we have to No big deal. ----- Original Message ----- From: Marek Goldmann <[email protected]> To: Ruby SIG mailing list <[email protected]> Cc: Sent: Wednesday, July 27, 2011 3:53:07 AM Subject: Re: Migration from RSpec 1.3 to RSpec 2.x Fun, I was looking at the release notes for latest datamapper and it seems they highlight "datamapper" over "data_mapper": http://datamapper.org/articles/datamapper-110-released.html It looks like they used the "dash version" earlier: http://datamapper.org/articles/datamapper-102-released.html http://datamapper.org/articles/datamapper-100-released.html ... IMHO the dash version is published for compatibility reasons. --Marek On 27 lip 2011, at 09:25, Vít Ondruch wrote: > Actually there are available both gems, datamapper as well as > data_mapper ... _______________________________________________ ruby-sig mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/ruby-sig _______________________________________________ ruby-sig mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/ruby-sig _______________________________________________ ruby-sig mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
