We have auto-requires for DSOs we link to.

Otherwise it doesn't match for weekly packages.

It wasn't meant to be checked in, but it yields slightly faster mock
builds on my system. And for some reason mock doesn't always kill
systemd-nspawn containers and I don't have time to debug that now.

We're not targeting el4 so we don't need them.

And use the "v_rc" release for weekly packages.

We can put everything together in a simple tgz file because that's what
people download on varnish-cache.org despite varnish's build system
outputting tar.gz files during `make dist`.

Go figure...

There's no call for bashisms, and much can be factored in a leaner way.

As we remove the default ``-S``, we no longer care about
handling the ``/etc/varnish/secret`` file.

Discussion in #84

Suggested in #87 to ensure that the network is fully initialised.

Unify the varnishncsa.service between the two.

This will make the service work out of the box by a simple
``systemctl enable varnishncsa``, as using the pidfile requires
``/var/run/varnishncsa`` to be created.

This is in line with the ``varnish.service`` anyway.