It doesn't make sense, drinking from the firehose like that.

It doesn't make much sense to have this by default.

Merge libvarnishapi1 into main varnish package, and rename
libvarnishapi-dev to varnish-dev.

Upgrade from 4.1.3 tested ok on xenial.

Simplify to get fewer packages to lug around.

RPM side is untested.

And to avoid misunderstandings, move the default versioning
all the way back to 3.0.

Mostly cosmetic.

This reverts commit 884d10fb.

This should be 5.0-specific, to not break builds of earlier
versions using the same packaging scripts.

There is no way to say "for all debian and ubuntu dists, use this", so
we must upload the same files to all platforms we care about.

if DEBVERSION undefined

If we can't do it properly because of support for older
platforms, we can document it.

Ref: #20

Fixes: #17

Closes: #806120

As found in
https://anonscm.debian.org/cgit/pkg-varnish/pkg-varnish.git/.
Fixes #27.

NB: The vcache user is not used yet.

This allow simple downgrade of Varnish package, because Varnish API might
not be forward compatible (new libvarnishapi1 with old Varnish).

Fix by hardcoding as suggested by Federico Schwindt.

This change also reverts the pid file name change that was an uninteded
side effect of a59b3bdd in Nov 2015. That commit renamed the pid file
from varnishd.pid to varnish.pid.

From a maintenance branch perspective it is not a good thing to change
these names, but I think going back to the original is the least painful way
moving forward. We'll have systems with sysv init for many years still.

Fixes: #22

In case I get hit by a bus some time.

It is present in 8.25 (stretch), but that isn't much help
on el7.

Fixes Varnish Cache issue 1903 on https://github.com/varnishcache/varnish-cache/issues/1903

Fix name column since cold/warm pushed it on the right

Reported by: 	TanguyPatte