Varnish project autumn cleaning
kly at redpill-linpro.com
Tue Nov 3 09:23:37 CET 2015
On Mon, Nov 02, 2015 at 10:22:30AM -0800, Jos Boumans wrote:
> +1 - hosting a build of every blessed varnish release for
> the popular platforms like redhat & ubuntu would be really
This is what packaging is.
> What’s the gating factor here for you? Time, cost, expertise?
> Is there a way the community can help you?
Who is "you"?
phk is not a packager. Kacper doesn't do the packaging either. So who
are you addressing here?
Packaging for most distros is already taking place, as Lasse pointed
out. With the steps Ingvar and ssm are taking, we'll have even better
coverage for Debian, Fedora and EPEL.
Lasse's mail is mostly about moving responsibility away from V-S over to
where it rightfully belongs: With the appropriate distros.
> > On Nov 2, 2015, at 10:10 AM, Kacper Wysocki <kacperw at gmail.com> wrote:
> > On Sat, Oct 31, 2015 at 10:51 AM, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
> >> --------
> >> In message <20151031092506.GB5176 at immer.varnish-software.com>, Lasse Karstensen writes:
> >>> With my VS hat on: Varnish Plus customers using community Varnish Cache
> >>> should contact support to find alternatives.
> >> The obvious alternative is to build from source.
The amount of times I've had to clean up the mess people have created
after using this "obvious alternative" far outweighs the times I've had
to deal with issues related to packages lagging a bit behind.
Building from source is an ops nightmare.
If your business is centered around Varnish, it might make sense. If
Varnish is just one of many many tools, then instead of telling people to
build from source, you might as well just attach the nginx user manual.
More information about the varnish-dev