gems:install rake task breaks if a versioned gem is required but an older version is install which satisfies another gem's dependency

Can you give a real example for this? The one you've shown doesn't make sense for several reasons:

• since mygem is first, it will be activated first. If your environment.rb says this and you're seeing mygem-1.0.0 activated, then something else is triggering it - maybe a stray require or gem statement in environment.rb?

• if mygem-2.0.0 is the latest version installed, then the stated dependency in yourgem will ALSO activate mygem-2.0.0, as the code (if all it has is a >= 1.0.0) will pick the highest version.

Thanks!

Hello David,

I am going through some of the old tickets to see if we can get some movement on these older issues. I was curious if you had an example for this as Matt asked for previously. Let us know if you have more information so we can check this out. I am marking this as incomplete for now, but feel free to update this when you have a minute.

thanks
Mike Riley
twitter.com/wdperson

Hello David,

Thanks for the update on this issue. I'll mark this as invalid as requested.

Mike Riley
twitter.com/wdperson