dependency problem

[emig]

Ataru has the following runtime dependencies:

• minitest
• kramdown
• thor

When the target gem also has the same runtime dependencies we encounter a dependency problem.

For example, having the target gem declared:

`kramdown ~> 1.1.4`

forces ataru's kramdown own depenency to be in the range 1.1.1 >= x < 1.2

Solutions?

[schultyy]

We worked around this in branch 49 by specifying only a lock on the major version of each dependency.

[emig]

First solution we thought of was to declare a big interval of accepted versions on ataru.

i.e:

spec.add_runtime_dependency "minitest", "~> 5"
spec.add_runtime_dependency "kramdown", "~> 1"
spec.add_runtime_dependency "thor", "~> 0"

This will enable a large range for dependencies compatible with the target. The range should then be at the semantic level of major version (*.0.0). This will limit the targets to have dependencies on the same range.

[madziaf]

So, the question is, is that a good solution or we should handle it differently?