We support building RPMs from a tarball, not directly from git (RPM
needs a tarball anyway, so requiring people to run make dist doesn't
seem onerous).

Remove autogen.sh invocation and remove explicit building of
documentation.  Both of these are done as part of make dist

Make sure the standard vmod ends up in the RPM

This had the unfortunate side effect of making builds in
non-world-readable directories not work correctly when run as root.

This reverts commit 07c4432b.

Conflicts:
	doc/sphinx/reference/varnishncsa.rst

git doesn't have the varnish-cache directory prefix, so drop that from
the spec file too.

Add libvgz to LD_LIBRARY_PATH in spec file and drop running varnishd
-C as that is done as part of the test suite.

If we were running as root, m00004 would fail as it would not be able
to read the files from the temporary directory.  To avoid this
problem, we now setuid to nobody if we are running as root.

until now, nobody seems to have noticed ?) and one to control where
we put the temporary allocations for gzip/gunzip.

all of it for gzip buffers.

The tarballs live on repo.varnish-cache.org, not
www.varnish-software.com any longer, so adjust spec file to match.

my section of hell for the dimwits who decided that switching off_t from
32 to 64 bits was too scary to contemplate.

Essentially ignores everything git status would list after a normal build.

vary-matching.  Varnish will adapt whatever we find to the clients
abilities as necessary.