Versions for required gems? about rubydora HOT 3 CLOSED

Are there particular gems you are having trouble with? I actually suspect that most of my dependencies are relatively version agnostic (with some lower bounds that would be nice to specify, but definitely require additional research).

That said, feel free to send a pull request or otherwise. I'm not against adding them, but adding arbitrary versions seems worse to me.

from rubydora.

I am not having issues personally, but I could see this being deployed to something like my company's ci machine and it grabs an old gem for some crazy reason and it breaks. Also, it is something that developers (like myself and team) like to see, since some of our projects have huge gem sets.

I will send a pull request, tossing in all the latest (or there-abouts, depending on the gem) stable versions. It is just a nicety to have in a gem, helps other developers know if it will work with their application or not at a quick glance. Also it makes sure you don't accidentally hit those lower bounds in the incompatible version area.

EDIT: Upon some chatter among a few devs here, until we find an issue, the current way you are not specifying versions shouldn't be an issue.

from rubydora.

Thanks, that definitely seems like the best approach to me. The dependencies are pretty major projects (perhaps to a lesser extent rest-client) and we're using only core functionality, so I'm confident that it won't be a problem for Rubydora.

If you do run into a dependency problem, though, please feel free to open a ticket to add versions for specific dependencies.

from rubydora.