01:35 gerald 

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

 

15:53 feld 

www/varnish5: Mark deprecated

 

13:14 mat 

Add DOCS options to ports that should have one.

Also various fixes related to said option.

PR:		230864
Submitted by:	mat
exp-runs by:	antoine

 

22:18 gerald 

Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.

This includes ports
 - featuring USE_GCC=yes or USE_GCC=any,
 - featuring USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and those
 - with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
   c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.

PR:		222542

 

08:37 amdmi3 

- Add LICENSE_FILE
- Switch to new test framework

Approved by:	portmgr blanket

 

19:03 linimon 

Adjust USES to fix builds on gcc-based architectures.

While here, pet portlint.

Tested for no regression on amd64.

Approved by:	portmgr (tier-2 blanket)

 

11:10 antoine 

Reduce dependency on the python2 metaport

PR:		225752
Submitted by:	Yasuhiro KIMURA

 

13:02 feld 

www/varnish5: Update to 5.2.1

Changelog:	https://varnish-cache.org/releases/rel5.2.1.html#rel5-2-1

MFH:		2017Q4
Security:	CVE-2017-8807
Security:	VSV00002

 

15:04 feld 

www/varnish5: Update to 5.2.0

Changelog:	http://varnish-cache.org/docs/5.2/whats-new/changes-5.2.html

 

16:10 mat 

Fixup GH_TAGNAME usage, and minor cleanup.

Sponsored by:	Absolight

 

00:10 feld 

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

 

18:30 feld 

www/varnish5: Update to 5.1.3

MFH:		2017Q3
Security:	https://varnish-cache.org/security/VSV00001.html

 

13:46 sunpoet 

Update devel/readline to 7.0 patch 3

- Bump PORTREVISION for shlib change

Changes:	https://cnswww.cns.cwru.edu/php/chet/readline/CHANGES
		https://lists.gnu.org/archive/html/bug-bash/2016-09/msg00107.html
		https://lists.gnu.org/archive/html/bug-readline/2017-01/msg00002.html
Differential Revision:	https://reviews.freebsd.org/D11172
PR:		219947
Exp-run by:	antoine

 

18:29 feld 

www/varnish5: Fix rc script reload functionality

VCL names can only use characters [A-Za-z0-9_]

MFH:		2017Q2

 

15:52 feld 

www/varnish5: Update to 5.1.1

Changelog:	http://www.varnish-cache.org/releases/rel5.1.1.html#rel5-1-1

PR:		217953

 

05:43 linimon 

Remove vestigial BROKEN_arm.  It does not do anything.  These ports all
build on aarch64 in any case.

Approved by:	portmgr (tier-2 blanket)

 

14:56 feld 

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>

 

14:03 marino 

www/varnish5, www/trafficserver: Document ncurses requirement

Approved by:	ncurses blanket

 

00:14 feld 

www/varnish5: Fix build

Error happened from delete / re-add via repocopy.

PR:		213761

 

17:05 feld 

www/varnish5: Re-add to ports tree as copy of varnish4

 

15:16 feld 

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

WWW: http://www.varnish-cache.org/