Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Shawn Starr
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

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Shawn Starr
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 To: Ruby SIG mailing list Cc

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Shawn Starr
Upstream has confirmed to me that data_mapper is the preferred name, as there is also rubygem-data_objects. - Original Message - From: Vít Ondruch To: ruby-sig@lists.fedoraproject.org Cc: Sent: Wednesday, July 27, 2011 3:04:32 AM Subject: Re: Migration from RSpec 1.3 to RSpec 2.x Dne

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Vít Ondruch
So it seems extlib can be migrated to the RSpec 2.x quite easily. See the attached patch. Btw the package build fails later due to YARD documentation build using Rake. I consider using of Rake as bad practice since Rakefiles are usually too tightly integrated with developer setup, therefore ca

datamapper vs data_mapper

2011-07-27 Thread Vít Ondruch
I have created upstream ticket for this: http://datamapper.lighthouseapp.com/projects/20609-datamapper/tickets/1520 Vit Dne 27.7.2011 10:05, Vít Ondruch napsal(a): > Probably, but its wrong anyway. For example sqlite3-ruby was renamed to > sqlite3. Nevertheless if you try to install sqlite3-ruby

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Vít Ondruch
Probably, but its wrong anyway. For example sqlite3-ruby was renamed to sqlite3. Nevertheless if you try to install sqlite3-ruby, it installs sqlite3 anyway. Not sure how is that done, but it should be probably reported upstream. Vit Dne 27.7.2011 09:53, Marek Goldmann napsal(a): > Fun, I was

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Marek Goldmann
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-10

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Vít Ondruch
Dne 27.7.2011 09:08, Marek Goldmann napsal(a): > On 27 lip 2011, at 09:04, Vít Ondruch wrote: >> Just out of curiosity, why you prefer "data_mapper" over "data mapper"? > Good question, especially when upstream calls it "datamapper": > > https://rubygems.org/gems/datamapper > > --Marek > > __

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Marek Goldmann
On 27 lip 2011, at 09:04, Vít Ondruch wrote: > > Just out of curiosity, why you prefer "data_mapper" over "data mapper"? Good question, especially when upstream calls it "datamapper": https://rubygems.org/gems/datamapper --Marek ___ ruby-sig

Re: Migration from RSpec 1.3 to RSpec 2.x

2011-07-27 Thread Vít Ondruch
Dne 26.7.2011 18:03, Shawn Starr napsal(a): > Thanks, all my current SRPMs are here at > http://www.sh0n.net/spstarr/fedora-work Thank you. > Note rubygem-datamapper is now rubygem-data_mapper so ignore the latter SRPM. > Just out of curiosity, why you prefer "data_mapper" over "datamapper"? V