Add dep-graph script

[maxbrunsfeld]

I added a simple script for generating a dependency graph of our packages using graphviz. Here's the current output:

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/72001270. This repo is managed by the 'Runtime Diego' team.

[vito]

Whoa, that's rad. Love the Garden bit: warden-linux importing the server half and executor importing the client half, and no one else. And sharing the protocol/domain models.

Also, lol runtime-schema.

[onsi]

Neato! But I think there's something wrong with the script. For exampl, route_emitter only speaks to methods in the lrp_bbs

[maxbrunsfeld]

Yeah it's just using go list, which reports that it imports the bbs package. It might compute the imports recursively.

[maxbrunsfeld]

Actually yeah, it's because route-emitter imports bbs, which imports all of the other runtime-schema packages to which route-emitter is connected in the graph.

[onsi]

Yes but the diagram explicitly draws a connection between it and all the sub packages of runtime-schema

Sent from my iPhone

On May 25, 2014, at 10:44 PM, maxbrunsfeld notifications@github.com wrote:

Actually yeah, it's because route-emitter imports bbs, which imports all of the other runtime-schema packages to which route-emitter is connected in the graph.

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

[maxbrunsfeld]

Right. It's debatable whether those lines should be present. They probably should though, because each of those packages is a dependency of route-emitter; they must all be godep'd into the repo in order to run it.

Edit -
This is notably different from the situation with the executor's dependence on garden, where it only requires certain packages from the repo.