The source code for the 'tidy' package
(http://tidy.cvs.sourceforge.net/viewvc/tidy/tidy/,
"Download GNU tarball") is distributed by the vendor in
somewhat atypical form. That is, it's just a CVS image, not
a tarball of source code released specifically for doing a
build.

In other words, the autotools, so-called, have not been run,
so the tarball has 'configure.in' and 'Makefile.in' but no
'configure' and 'Makefile'.

To accomplish that, we have run build/gnuauto/setup.sh,
which comes in the upstream (3rd party) tarball. (But before
doing that, we have applied very light changes to the
upstream files.)

The light changes we just mentioned can be seen in
patch_human_generated_changes.ALREADY_APPLIED. We include
that patch in our tarball mainly for informational purposes,
in case a different developer (or this developer) needs to
repeat the process in the future for yet a later release.
The essential change, as seen in the patch named above,
is to add AM_MAINTAINER_MODE to 'configure.in' ;

After running the setup.sh, we have created a second patch,
"patch_for_easyapache_step", which Easyapache will apply
before it builds 'tidy'. See Cpanel/Easy/OptLib/tidy.pm ,
q.v. That patch represents the delta between the pristine
3rd party distribution of 'tidy', and the same tree *after*
our run of the setup.sh script. (The pristine upstream
distribution can be found in our tidy.pm.tar.gz in directory
3rdparty/tidy.)

Another weirdness (one might call it a side-effect) of that lack
of formal release that there are no release numbers. Instead,
releases are identified by a date, e.g., "6 November 2007"
(the "release" prior to this case) and "25 March 2009" (the
release for this case).
