anchor.diff:  unpacks the package. The source directory tree is designed for parallelism,
   the different build types may coexist in the same source tree.
   
  -This makefile is run first from the source directory root (e.g. src/),
  +This makefile is run first from the source directory root (e.g. `src/`),
   and must be performed only upon updates to the source packages.
   The resulting manifest can be compared to the previously created manifest
   to determine if the sources have been updated.
   
  -Makefile.preconfig should follow immediately when the manifest changes.
  +`Makefile.preconfig` should follow immediately when the manifest changes.
   
   == Phase 2: Preconfigure Sources
   
    $ cd src/
  - $ make -f Makefile.preconfig [BLD={type}]
  + $ make -f ../mak/Makefile.preconfig [BLD={type}]
   
   Prepare configuration scripts of packages, particularly from source control
   where autoconf etc have not been invoked yet.
   
  -This makefile is run after Makefile.gather from the source directory root,
  +This makefile is run after `Makefile.gather` from the source directory root,
   and must be performed following updates to the source packages as indicated
   by manifest changes. Only source code packages corresponding to the specific
   BLD target are updated.
   
   The result of this step is suitable for archive, or escrow and distribution
  -to multiple build systems, beginning at the Makefile.build step.
  +to multiple build systems, beginning at the `Makefile.build` step.
   
   == Phase 3: Build Sources
   
    $ cd bld/
  - $ make -f Makefile.build [BLD={type}] [TAG={-suffix}]
  + $ make -f ../mak/Makefile.build [BLD={type}] [TAG={-suffix}]
   
   Build all components described by the manifest into the intermediate/
   temporary installation tree, using that intermediate tree as the component
  
positive.code: which are reasonably stable and up to date. On Windows,
  every component must be built from source.
  
  The build target is /opt/pivotal/webserver/httpd-2.4/
  on Linux and Windows, but is relocatable. Each has a
  long pathname, e.g. httpd-2.4.25-$bldno/ which is
  symlinked from the 'expected' path. Non-release builds
  have additional pathname components such as -snapshot,
  -bleed, etc, and may have a TAG to distinguish two
  otherwise apparently identical builds.
  
  Build \{pkg} reflects the particular component, either
  the offical designation (httpd-2.4.25/), an indication
  of interim packages (httpd-2.4.26-rc1/), or the exact
  province of the file (httpd-2.4.26-dev-r1872199/)
  
  Several \{bld} schemas are expected; 'release' for the
  official packages, 'candidate' for packages anticipated
  for release, 'snapshot' for the working trees of the
  component's current maintenance trees, and 'bleed' for
  
negative.code: checkout revision, or continuous build revision number. By default there is
  no suffix tag.
  
  This makefile is run after `Makefile.gather` and `Makefile.preconfig` and may
  be based on a snapshot of the build tree from those two previous steps from
  another continuous build job.
  
  This makefile must be run from the build (not source) subdirectory, such
  as `bld/`. The build tree uses the same component directory names as the
  source tree. The components are initially installed into the DESTDIR
  which is the `../dst/httpd` component directory name with the TAG variable
  suffixed. SRCDIR references the source tree (typically `../src`) and would
  typically not need to be overridden.
  
  The TARGET directory, `/opt/pivotal/webserver/$(httpd_srcdir)$(TAG)` would
  typically not be overridden, and refers to the anticipated installation
  path of the resulting package.
  
  == Phase 4: Test Source and Intermediate Installation
  
   $ cd bld/
   $ make -f ../mak/Makefile.test [BLD={type}] [TAG={-suffix}]
  
  Test all components described by the manifest and the intermediate/
  temporary installation httpd server.
  