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/tree/master/fixtures/go_ldflags/src/go_app)
  -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: └── manifest.yml
  ```
  
  When you configure your project like this, set the environment variable `GO_INSTALL_PACKAGE_SPEC` 
  to `$MODULE_NAME/$MAIN_PACKAGE_PATH`.
  
  If the module name for the above `app-package-name` app is `example.com/user/app-package-name`,
  
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.
  
  The following is an example `Gopkg.toml` file:
  
  ```toml
  [[constraint]]
  