-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing development dependencies #33
Comments
It should install them automatically. Do you want to do it manually sometimes? |
It gives me back a "Please run 'bundle install'", and then prompts to submit my test results (even though they didn't successfully run). The gem I was trying is magickly, btw. Thanks! |
Ah ok. Bundler isn't supported in rubygems-test, as it's not the preferred method of managing dependencies in a gem. Rubygems has built in support for managing development dependencies. |
Ah ok I have a theory... my installed gem versions meet the requirements listed in the gemfile (as well as the Gemfile), but not the versions in the Gemfile.lock. |
Let us know what resolves this; I'm preparing a faq in my free time for users of bundler, rspec and other tools that aren't as obvious of how to set rubygems-test up. |
Ok, so for v1.1.3 of magickly, I didn't have a version of rake set explicitly in my Gemfile, and the dependencies I explicitly listed only had Not sure the optimal path here - basically, the difficulty is the difference in how Bundler and Rubygems handle requirements. |
Sorry to get back to you so late on this, it's been a busy month. The rake issue is one we need to address and, well, I'm not quite sure how to handle that just yet, namely how rake is run from the command line. So to summarize, the issue here is:
|
Right - since I don't want to force the users of my gem to use a particular version of rake, I don't have it explicitly specified in the gemspec. |
Running a gem's tests will usually require its development dependencies, so it would be great if there were an additional command to do so.
The text was updated successfully, but these errors were encountered: