Unsustainable dependency graph

[toqueteos]

Take a look at http://godoc.org/github.com/shurcooL/Conception-go?import-graph&hide=2

All those gists made repos are not gonna work in the future.

[dmitshur]

Yes, Conception-go has a large number of dependencies. That is expected because its scope is quite large.

I am actively maintaining and watching all of the dependencies. The Travis build ensures the project builds with latest versions. If there's ever a problem upstream, I fix it quickly. So I don't think it's a problem.

As far as Go packages with "gist" in the name, they're all contained in a single git repo that I host, so they're only going away when they're no longer needed, not sooner. See https://github.com/shurcooL/go/tree/master/gists. I've been slowly refactoring my code to move those packages so they have a better import path, or deleting unneeded ones. For example, see shurcooL/go@6a87214.

[toqueteos]

That's good to know. I just saw the repo and I always tend to check the dependency graph first and was.. astonished.

If refactoring is in progress then there's nothing to worry. Closing issue.