anchor.diff:        - cflinuxfs2
        ```
   
  -## <a id='deploying-with-custom-buildpacks'></a>Deploying With a Custom Buildpack ##
  +## <a id='deploying-with-custom-buildpacks'></a>Deploying Apps with a Custom Buildpack ##
   
   Once a custom buildpack has been created and pushed to a public git repository, the git URL can be passed via the cf CLI when pushing an application.
   
  
positive.code: 
  For more information, see the documentation at the [buildpack-packager Github repo](https://github.com/cloudfoundry-incubator/buildpack-packager).
  
  #### Uploading the buildpack
  
  Once you have packaged your buildpack using `buildpack-packager`, you can upload the resulting `.zip` file to your instance of Cloud Foundry:
  
  <pre class="terminal">
  $ cf create-buildpack BUILDPACK PATH POSITION [--enable|--disable]
  </pre>
  
  <%=vars.link_adminguid_buildpack%>
  ### <a id='specifying-default-versions'></a> Specifying Default Versions ###
  
  As of `buildpack-packager` [version 2.3.0](https://github.com/cloudfoundry/buildpack-packager/releases/tag/v2.3.0), you can specify the default version for a dependency by adding a `default_versions` object to the `manifest.yml` file.
  
negative.code: 
  ## <a id='packaging-custom-buildpacks'></a> Packaging Custom Buildpacks ##
  
  Cloud Foundry buildpacks work with limited or no internet connectivity. A Cloud Foundry operator can use the [buildpack packager](https://github.com/cloudfoundry-incubator/buildpack-packager) to give the same flexibility to custom buildpacks, enabling them to work in partially or completely disconnected environments.
  
  ### Using the Buildpack Packager
  
  1. Create a manifest.yml in your buildpack.
  1. Run the packager in cached mode: 
    <pre class="terminal">$ buildpack-packager --cached</pre>
  