I'm currently playing with getting spork working for a merb app we're working on - I'm pretty sure i've managed to split up the bootloading process of merb into prefork and each_run.
However, i'm running into a problem that appears to be mostly unrelated to merb. Here's the flow as I follow it:
spork rspec (starts spork server)
I'm not quite sure why no-one else is running into this issue (or at least, no-one seems to be running into it and posting anything about it on the internet)
I'm probably going to work around the problem using a slightly messy hack for the moment, but I'm unsure what would be a good clean way to fix this.
this is really weird: I've never run into this, that, now that you mention it, it's weird that I haven't!
I would say that this problem lies on the RSpec side: RSpec shouldn't be sending the --drb parameter over. I will have to take a look and see why it doesn't happen in rails.
Can you run the cucumber features and see if you can reproduce it with those? (Spork is quite heavily tested with integration tests, I run them against versions of rails 2.1.0 through 2.3.5)
On installing rspec 1.3.2 in a rails 2.3 app, I ran into this also. I'll figure out some hack around, but definitely in a console, Spec::Runner.options starts the infinite loop.
I ended up upgrading to rails 3...
I wound up getting rid of spec.opts and adding the options to the :opts parameter in Guard.