move tools.go to sub-package (#2300)

`godep` by default pulls in all dependencies regardless of build tags.  If `tools.go` is in our main package, that can cause unnecessary dependencies to be pulled into others' repos that otherwise don't need them.  Moving it to an unused sub-package appears to fix this problem.
This commit is contained in:
dfawley 2018-09-11 10:33:48 -07:00 committed by GitHub
parent 46ee6abebf
commit d42ac64492
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions

View File

@ -18,12 +18,12 @@
*
*/
// This file exists to cause `go mod` and `go get` to believe these packages
// are dependencies, even though they are not runtime dependencies. This means
// they will appear in our `go.mod` file, but will not be a part of the build
// unless the "tools" build tag is specified.
// This package exists to cause `go mod` and `go get` to believe these tools
// are dependencies, even though they are not runtime dependencies of any grpc
// package. This means they will appear in our `go.mod` file, but will not be
// a part of the build.
package grpc
package tools
import (
_ "github.com/client9/misspell/cmd/misspell"