This is the Varnish high-performance HTTP accelerator.
Documentation and additional information about Varnish is available on
http://varnish-cache.org/docs/index.html
Technical questions about Varnish and this release should be addressed
to <varnish-dev@varnish-cache.org>
Questions about commercial support and services related to Varnish
can be directed here: https://www.varnish-software.com/contact-us
===> The following configuration options are available for varnish4-4.1.11_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
www/varnish4: Deprecate and set expiration date to 2022-12-31
Unsupported upstream since 2019
PR: 266646
Approved by: portmgr (maintainer timeout, 2+ weeks)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
www/varnish[4|6|7]: Chase deprecated CPE information
According to NIST CPE dictionary the old CPE varnish-cache:varnish
has been deprecated by varnish-cache:varnish_cache.
Approved by: portmgr (blanket)
Obtained from: https://nvd.nist.gov/products/cpe/detail/728797
devel/autoconf: update to 2.71
- Copy devel/autoconf to devel/autoconf2.69.
- Update devel/autoconf to 2.71.
- Allow ports to use 2.69 with USES=autoreconf:2.69.
PR: 258046
Exp-run by: antoine
www/varnish4: fix build on powerpc64 head
Don't use -Werror:
vmod_std_conversions.c:198:10: error: implicit conversion from 'long' to
'double' changes value from 9223372036854775807 to 9223372036854775808
[-Werror,-Wimplicit-int-float-conversion]
www/varnish4 www/varnish5: Change MASTER_SITES to GITHUB
- Now properly use autotools
- rst2man is a required build dependency
Requested by upstream as the current mirror is being retired
MFH: 2017Q3
www/varnish4 www/varnish5: Change default hash algorithm
The default hash algorithm as of Varnish 2.1 is "critbit". The FreeBSD
varnish ports/packages have run the varnish daemon with the "classic"
algorithm due to an oversight. This update corrects the default to
adhere to the recommendation of upstream.
Submitted by: Mark Staudinger <mark staudinger AT nyi net>
Use USES=pathfix where applicable.
PR: 213195
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D8093
www/varnish4: Fix race condition on start
varnishlog and varnishncsa had a race condition with varnishd on
startup as they will notice varnishd's leftover _.vsm file and try to
connect to varnishd but occasionally fail due to varnishd not being
fully operational yet. By adding "-t off" flag as default to varnishncsa
and varnishlog they will wait indefinitely for varnishd to start up
instead of just exiting.
Other bugs fixed:
* varnishncsa_logformat in rc.conf mostly works
Unfortunately due to shell expansion we still cannot pass
quotes (") so if you need those in your log format you will have to
(Only the first 15 lines of the commit message are shown above )
www/varnish4: varnishlog produce ascii logs by default
Before version 4.1.0 the logs were ascii. Return that behavior to not
surprise users who upgrade.
Improve shebangfix framework
- Support multiple values in *_OLD_CMD, i.e. we can now fix both
"/usr/bin/python" and "/usr/bin/env python" at the same time
- Default *_OLD_CMD values are now always appended, so you don't need to specify
them in individual ports
- Add lua support (depends on USES=lua)
- Add more default values, such as "/usr/bin/env foo" for python, perl, bash,
ruby and lua
- Shebangfix now matches whole words, e.g. we will no longer (erroneously)
replace "/usr/bin/perl5.005" with "${perl_CMD}5.005" (but "/usr/bin/perl -tt" is
still (correctly) replaced with "${perl_CMD} -tt")
Note that *_OLD_CMD items containing spaces must now be quoted (e.g.
perl_OLD_CMD=/bin/perl /usr/bin/perl "/usr/bin/env perl")
Update shebangfix usage according to new rules in many ports:
- Remove *_OLD_CMD for patterns now replaced by default
- Quote custom *_OLD_CMD which contain spaces
Fix shebangfix usage in many ports (irrelevant to infrastructure change):
- Remove redundant SHEBANG_LANG (no need to duplicate default langs)
- Remove redundant *_CMD (such as
python_CMD=${LOCALBASE}/bin/python${PYTHON_VER} when USES=python is present)
- Never use *_OLD_CMD in REINPLACE_CMD matchers, these should always look for
exact string
Approved by: portmgr (bapt)
Differential Revision: D3756
Switch default python_CMD used by shebangfix to ${PYTHON_CMD} for ports
using python
PR: 201077
Reviewed by: mat
With hat: portmgr
Differential Revision: https://reviews.freebsd.org/D2955
Fix startup script order:
varnishncsa and varnishlog require varnishd to start successfully
mat reported some latency between starting varnishd and creation of
the _.vsm file used for communication, so a start_precmd has been added
to varnishncsa and varnishlog.
PR: 201586
Differential Revision: https://reviews.freebsd.org/D3208
Require python as a run dependency, too
python is required for you to be able to build custom vmods and also for
other vmods in the ports tree to build. Better off including the
requirement here as we ship the vmodtool.py utility and do not want to
surprise end users.
shebangfix was included as the default shebang on vmodtool.py is
/usr/bin/env python which is not going to work unless the lang/python
metaport is installed, which is not included with USES=python. Instead
we just rewrite this to whichever the default system python intepreter
is (PYTHON_VERISON).
Add varnishd_extra_flags option to permit passing additional flags to
varnishd
Clean up rc scripts per rclint recommendations
Differential Revision: https://reviews.freebsd.org/D2605