anchor.diff:  reference as you add elements to the release.
   
   Go through any scripts you have created and note the files cited by each script.
  +_note package path_ and _go through all job templates_.
   The names of these files must be added to the `packages` block of the job spec.
   In our example, they are `ardo_web` and `ruby_1.9.3`.
   
  
positive.code: 
  ### <a id="..."></a> Create packaging scripts ###
  
  The packages you have been creating represent software that BOSH needs to
  install on VMs at deploy time.
  That is accomplished by the `packaging` script within each package.
  
  Every packaging script must install the software for the package it belongs to,
  and also invoke any package dependencies.
  Use your dependency graph to determine which dependencies belong in each
  packaging script.
  
  For a start on writing packaging scripts, study the examples.
  Begin packaging scripts with a `set -e -x` line to aid debugging at compile time.
  
  _explicitly say to write all packaging scripts now?_
  _include packaging scripts inline?_
  
  ### <a id="..."></a> Create packaging specs ###
  
  
negative.code: dev releases.
  * Upload blobs to a public blobstore before you create a final release.
  
  Normally, all the binaries you record in your packaging specs should be added to a local blobstore.
  
  ### <a id="..."></a> Create a local blobstore  ###
  
  