Should we have something like a ripple.config and a ripple.config.lock?

[agross]

I'd like to spin off a discussion whether ripple should employ the same pattern found in Ruby's bundler gem:

• A ripple.config that defines the dependencies + versions for the ripple solution and
• a ripple.config.lock that fixes the solution dependencies and their transitive dependencies to specific versions

As the ripple team has experience with Ruby I wonder if that design has been discussed. I'd argue it has a couple of advantages over the current ripple.config that contains all dependendies (solution deps + transitive deps):

• You get a clear picture what the solution requires just by looking at the ripple.config
• If you care about transitive deps, look at ripple.config.lock

My issue with the current design is that if you move higher up in the solution tree (towards the "package composition root"), the more entries you will have in the ripple.config, making it harder to see what's going on.

[jeremydmiller]

That's definitely not a new conversation, and we discussed that quite a bit last month at Pablo's Fiesta. I'm hoping that Josh remembers more of the conversation to share here than I did. I think that by and large the group did like the idea.

On Nov 13, 2013, at 7:37 AM, Alexander Groß notifications@github.com wrote:

I'd like to spin off a discussion whether ripple should employ the same pattern found in Ruby's bundler gem:

A ripple.config that defines the dependencies + versions for the ripple solution and a ripple.config.lock that fixes the solution dependencies and their transitive dependencies to specific versions As the ripple team has experience with Ruby I wonder if that design has been discussed. I'd argue it has a couple of advantages over the current ripple.config that contains all dependendies (solution deps + transitive deps):

You get a clear picture what the solution requires just by looking at the ripple.config If you care about transitive deps, look at ripple.config.lock My issue with the current design is that if you move higher up in the solution tree (towards the "package composition root"), the more entries you will have in the ripple.config, making it harder to see what's going on.

— Reply to this email directly or view it on GitHub.