anchor.diff:  This can be used to embed the commit SHA or other build-specific data directly
   into the compiled executable.
   
  +For a sample Go app,
  +see the [go-buildpack](https://github.com/cloudfoundry/go-buildpack)
  +repository on GitHub.
  +
   ## <a id='c_dependencies'></a>C Dependencies ##
   
   The Go buildpack supports building with C dependencies using [cgo](https://golang.org/cmd/cgo/). You can set config vars to specify cgo flags
  
positive.code: ```
  
  ### <a id='with_dep'></a>Push an App with dep ###
  
  If you use [dep](https://github.com/golang/dep) to specify or package your dependencies,
  make sure that you have created a valid `Gopkg.toml` file in the root directory of your app by running `dep init`.
  
  
negative.code: This will generate a `vendor` directory and a `Gopkg.lock` file specifying the latest compatible versions of your dependencies.
  You must have a `Gopkg.lock` file when pushing a vendored app. You do not need a `Gopkg.lock` file when deploying a non-vendored app.
  
  ####<a id='dep_app'></a>dep
  
  * [Sample Go app with dep](https://github.com/cloudfoundry/go-buildpack/tree/master/fixtures/godep)
  
  An example `Gopkg.toml` file:
  
  ```toml
  [[constraint]]
  