anchor.diff:  `<package_name>/**/*` to deep-traverse the directory in `src` where
   the source code will reside.
   
  -Observe how these conventions are followed in the examples.
  +Update the spec for each package.
  +Refer to the example specs below for guidance.
   
   #### <a id="pkg-spec-libyaml"></a> Example libyaml package spec ####
   
  
positive.code:   --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
  
negative.code: 
  ## <a id="pkg-skeletons"></a> Create Package Skeletons ##
  
  Packages give BOSH the information needed to prepare the binaries and
  dependencies for your jobs.
  
  When first created, a package is a _skeleton_: an empty structure that fills up
  as release creation progresses.
  