anchor.diff:    --without development test
   ~~~
   
  -
  -Like control scripts, writing packaging scripts is one of the heavier tasks
  -entailed in creating a release.
  -
   ### <a id="update-job-specs-with-deps"></a> Update job specs with dependencies ###
   
   The dependency graph reveals runtime dependencies that
  
positive.code: 
  Within each package directory is a `spec` file which states:
  
  * The package name.
  * The package's dependencies.
  * The location where BOSH can find the binaries and other files that the package needs at compile time.
  
  Use your dependency graph to determine which dependencies belong in each spec.
  Your personal preferences and style as a developer also play a role here.
  Consider our example: the spec for Ruby lists `rubygems` and `bundler` as dependencies along
  with Ruby itself.
  Some Ruby developers would do it this way; others would not.
  
  Remember not to depend on the presence of libraries or other software on the stemcells that
  BOSH uses to create VMs.
  This maximizes the portability of your release across different versions of stemcells.
  
  To correctly describe binary locations in the `files` block of the spec:
  
  * Find the official site for the binary in question.
  For example, Ruby might be at `http://cache.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p484.tar.gz`.
  
negative.code: `BOSH_INSTALL_TARGET`.
  See how this is done in the example packaging scripts.
  
  Like control scripts, writing packaging scripts is one of the heavier tasks
  entailed in creating a release.
  Write your packaging scripts now.
  Refer to the examples below for guidance.
  
  #### <a id="pkg-script-libyaml"></a> Example libyaml packaging script ####
  
  