T
Tony Arcieri
[Note: parts of this message were removed to make it a legal post.]
We're trying to support both MRI and JRuby for a project, and have a number
of "internal" gems our software is packaged into.
What would be *great* is a means to have variadic gem dependencies, selected
based on the current RUBY_ENGINE. Many of the gems we need on MRI are
irrelevant on JRuby or require JRuby-specific alternatives.
Since I don't have this, I've ended up making two gem servers, one for MRI
and one for JRuby. I've ended up loading the JRuby server with some "dummy"
gems which don't actually do anything but fulfill the gem dependencies for
gems that aren't needed on JRuby. This seems like a bit of a hack.
Does anyone have a better solution for this?
We're trying to support both MRI and JRuby for a project, and have a number
of "internal" gems our software is packaged into.
What would be *great* is a means to have variadic gem dependencies, selected
based on the current RUBY_ENGINE. Many of the gems we need on MRI are
irrelevant on JRuby or require JRuby-specific alternatives.
Since I don't have this, I've ended up making two gem servers, one for MRI
and one for JRuby. I've ended up loading the JRuby server with some "dummy"
gems which don't actually do anything but fulfill the gem dependencies for
gems that aren't needed on JRuby. This seems like a bit of a hack.
Does anyone have a better solution for this?