Lock mismatch immediately after dep init

[carolynvs]

What version of Go (go version) and dep (git describe --tags) are you using?

$ go version
go version go1.8.3 darwin/amd64

$ git describe --tags
v0.1.0-295-gd558b52

What dep command did you run?

dep init && dep status

What did you expect to see?

I expected that after a fresh init and no changes, that the lock would be valid.

What did you see instead?

Lock inputs-digest mismatch. This happens when Gopkg.toml is modified.
Run `dep ensure` to regenerate the inputs-digest.

I believe the problem is that when we run dep init, it detects external tools and sets the analyzer name to dep+import. When dep ensure is run, it doesn't use any importers so the analyzer name is just dep, immediately triggering a lock mis-match.

We will eventually run the analyzers during ensure, #821. Once we have that in place and both init and ensure use the importers, the hash won't mismatch.

[sdboyer]

in general, the purpose of that field (along with the associated version number) is to uniquely identify a particular analyzer algorithm. if the algorithm is actually the same, depending on some configuration (e.g., use the external tools importers or don't), then there's no need for the name to be any different.