anchor.diff:  * Up to now all we have is a mention of the package in the job spec.
   * Now we create the job package itself:
   
  -  `bosh generate package ardo-web`
  -
  -* The package contains a `spec` and a `packaging` script, both empty when
  -the package is newly created.
  +  `bosh generate package ardo_web`
  +
  +* The package contains stubs for a `spec` and a `packaging` script.
   * Next, put useful information into `spec` and `packaging`.
   
   ### <a id="..."></a> Update the job package spec with dependency information ###
  
positive.code: 
  For each blob, run:
  
  `bosh add blob <path> <package_name_as_prefix><filename>`
  
  You construct this command by taking the same information found in the spec for each package in the
  `packages` directory.
  
negative.code: * 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`.
  
  * Download the binary from the official location and make sure the file hash matches.
  
  * Record the binary name including version number, with a slash and the binary filename concatenated to it.
  It's a good idea to cite the official URL in a comment, in the same line.
  
  BOSH interprets the locations you record in the `files` section as being either in the `src` directory or
  in the `blobs` directory. (BOSH looks in `src` first).
  When you add the actual blobs to a local blobstore (see the next section), BOSH populates the `blobs` directory with the
  correct information.
  
  Observe how these conventions are followed in the examples.
  
  