Does Guard need to be a development dependency?

[bfoz]

Sure, guard is great and all, but not everyone uses it. Does it really need to be listed as a development dependency?

Making guard a dependency forces 'bundle install' to install it, and not everyone wants that. I don't mind, but I can see how others might.

I'm happy to make the change and submit a pull request.

[meltingice]

Running guard outside of bundler is typically frowned upon, and it needs to be listed as a dependency of some type in order to use it with bundle exec. Installing it shouldn't be much of a problem if your Ruby environment is setup in a sane way.

That said, that reminds me that I need to list rb-fsevent as OSX only. Making that change to the gemspec...

[bfoz]

You're right that installing it isn't much of a problem, but it does add cruft to one's environment. I can see it being an annoyance for people who use any of the guard alternatives (or prefer to run rspec manually); they end up with installed dependencies that they're never going to use. But, it should only be a minor annoyance.

Thanks for taking the time to reply.