Migration from RSpec 1.3 to RSpec 2.x

[Vít Ondruch]

Dne 13.2.2012 20:40, Mo Morsi napsal(a):
> On 01/25/2012 04:46 AM, Vít Ondruch wrote:
>> Hi guys,
>>
>> It seems that we have almost eliminated usage of RSpec 1.x:
>>
>> $ repoquery --repoid=rawhide-source --arch=src --whatrequires 
>> 'rubygem(rspec)'
>> rubygem-ffi-0:1.0.9-2.fc16.src
>> rubygem-linode-0:0.6.2-1.fc15.src
>>
>> $ repoquery --repoid=rawhide --whatrequires 'rubygem(rspec)'
>> aeolus-conductor-devel-0:0.4.0-2.fc17.noarch
>>
>> $ repoquery --repoid=rawhide-source --arch=src --whatrequires 
>> rubygem-rspec
>> rubygem-daemon_controller-0:0.2.6-2.fc17.src
>>
>> $ repoquery --repoid=rawhide --arch=src --whatrequires rubygem-rspec
>>
>>
>> The only remaining packages are:
>> rubygem-ffi (bkearney) - seems to be just packaging bug: 
>> https://bugzilla.redhat.com/show_bug.cgi?id=760009
>> rubygem-linode (stahnma) - upstream is already RSpec 2.x compatible, 
>> it is FTBFS currently and it would deserve update anyway
>> aeolus-conductor-devel (mmorsi, clalance, sseago) - Hm, are 
>> rubygem(rspec-rails) 2.6 compatible with RSpec 1.x? I doubt it ...
>> rubygem-daemon_controller (pwu) - It seems there should not be issue 
>> running with RSpec 2.x, although I did not tested it.
>>
>>
>> Could we move forward and let the rubygem-rspec to follow the 
>> upstream RSpec version and Require: rubygem(rspec-core)?
>>
>
>
> +1, lets move forward with this. I'm in the process of updating the 
> aeolus-conductor codebase to work against ruby 1.9.3 and will look 
> into incorporating an update to rspec 2 into this.
>
> Since linode, ffi, and daemon_controller have been taken care of and 
> we've long announced the update to rspec2 in F17, lets perform the 
> final cutover. If there are issues going forward, we can easily 
> introduce a rspec1 compat package.
>
>   -Mo
>

Mo,

You mentioned in the packaging discussion that you have prepared patches 
for rubygem-rspec to migrate them to RSpec 2.x, is that right? Could you 
share them with us?

Vit