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: 3 directories, 9 files
  </pre>
  
  This modular approach, with a separate package for each dependency,
  provides maximum reusability along with clear structure.
  It is not mandatory; what packages to create is a matter of preference.
  You could even opt to put all the dependencies together in a single package,
  though that is not recommended.
  
  **Note**: Use of the `pre_packaging` file is not recommended, and is not discussed in this tutorial.
  
  
negative.code: `<package_name>/**/*` to deep-traverse the directory in `src` where
  the source code will reside.
  
  Update the spec for each package.
  Refer to the example specs below for guidance.
  
  #### <a id="pkg-spec-libyaml"></a> Example libyaml package spec ####
  
  