I agree. There is probably no reason not to have both or?
----- Original Message -----
From: "Vít Ondruch" <vondruch(a)redhat.com>
Sent: Friday, November 28, 2014 12:15:20 PM
Subject: Re: rspec 3.1.x in rawhide
Dne 10.11.2014 v 14:59 Mamoru TASAKA napsal(a):
- Or not, you can use BuildRequires(rspec2). Note that
2.x version rspec (script) is renamed to %_bindir/rspec2,
you'll probably have to do
$ rspec2 spec/
Used the rspec2 command for the first time, I have strange feeling about
it. Shouldn't we provide also plain rspec command for rspec2?
Let me explain. When you install RSpec 2.x and RSpec 3.x side by side by
gem install, you'll get single rspec executable. You can later choose
which version you actually want to execute by something like "rspec
_2.2_". So while I agree that rspec2 is a bit simpler than the previous
command, I'd say that the rspec command should be available as well,
since when only RSpec 2.x is available on your system, it is unexpected
to don't have the rspec command available, otherwise user experience is
broken IMO. Thoughts? I'll probably file bug later ...
ruby-sig mailing list