Gem dependencies issue

Ok, I’m trying to install gem A. I could give you the names of the gems,
but
I doubt it matters.

Anyway, gem A requires gems B and C, any versions. So it goes and gets
the
newest version of B and installs it, no problem.

Then it goes to install C, but C requires a particular (old) version of
B.
So it croaks and refuses to install.

I’m sure there’s an easy solution to this, but I don’t know it…if I
wanted this much pain, I’d have two wives…

On 10/29/2010 4:55 PM, Andrew W. wrote:

wanted this much pain, I’d have two wives…
What happens if you explicitly install C first and then try to install
A?

-Jeremy

On Oct 29, 7:55pm, Andrew W. [email protected] wrote:

I’m sure there’s an easy solution to this, but I don’t know it…if I
wanted this much pain, I’d have two wives…

Give gem names, it matters.

RubyGems dependency resolution is not very smart, but is not dumb.
Either the gem authors didn’t carefully mark their dependencies or
RubyGems is doing something wrong.

One example of that was Rails and Rack. Search for examples in the
past about that (one of the reasons of bundler been born).

Now, show us exact gem names and versions, exact “gem install A –
debug -V” output and we can talk, just me, is cheaper than couple
therapy :slight_smile:

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs