On Fri, Jul 31, 2009 at 4:57 AM, Balint Erdi<balint.e...@gmail.com> wrote:
>
> One possible workaround is to put the rspec and rspec-rails lines into
> the environment file for the test env. (test.rb), but that seems to
> defeat the goal of having all dependencies in one place so that it is
> clear and gem-related rake tasks can be conveniently run. (I am using
> rails 2.3.2, rspec 1.2.8, rspec-rails 1.2.7.1)

Actually, I think it's pretty sensible.  That's where I have mine.
This is an environment-specific dependency.  If you're never going to
run in a test environment on a particular server, you don't need RSpec
and there's no reason for the gem tasks to install it.  (If you will,
then the deployment is just a matter of setting the environment
variable first: "RAILS_ENV=test rake gems:install")


-- 
Have Fun,
   Steve Eley (sfe...@gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users

Reply via email to