FreeBSD ports tree https://cgit-dev.freebsd.org/ports/atom?h=2018Q1 2017-11-30T06:13:34Z 2017-11-30T06:13:34Z Mark Linimon linimon@FreeBSD.org 2017-11-30T06:13:34Z urn:sha1:bf43557044604cb6487fc1aa24ce2c210ae789da armv7, mark them so. This is part two of a multipart commit to bring armv7 ports to parity with armv6. Approved by: portmgr (tier-2 blanket) Obtained from: lonesome.com -exp run 2017-09-10T20:55:38Z Gerald Pfeifer gerald@FreeBSD.org 2017-09-10T20:55:38Z urn:sha1:e59c88cece035a155debaf8996ce8f20adabd78b (via Mk/bsd.default-versions.mk and lang/gcc) which has moved from GCC 5.4 to GCC 6.4 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, c++11-lib, c++11-lang, c++14-lang, c++0x, c11, or gcc-c++11-lib. PR: 219275 2017-05-22T22:29:17Z Mark Linimon linimon@FreeBSD.org 2017-05-22T22:29:17Z urn:sha1:197f08abf4fd25e8493f6391ed2c5cac9671e9bb was a stub, provide a real one. While here, pet portlint. Approved by: portmgr (tier-2 blanket) Reported by: swills 2017-04-01T15:23:30Z Gerald Pfeifer gerald@FreeBSD.org 2017-04-01T15:23:30Z urn:sha1:04d6f52202c61a48690e73e65879001d2ee3adc5 lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some circumstances such as versions of FreeBSD or platforms). This includes ports - with USE_GCC=yes or USE_GCC=any, - with USES=fortran, - using using Mk/bsd.octave.mk which in turn has USES=fortran, and - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang, c++11-lang, c++0x, c11, or gcc-c++11-lib. PR: 216707 2016-11-20T09:38:08Z Gerald Pfeifer gerald@FreeBSD.org 2016-11-20T09:38:08Z urn:sha1:89f8b052147a980faa4f4419d8444f0c7073c997 lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some circumstances such as versions of FreeBSD or platforms). In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang, c++11-lang, c++0x, c11 requested via USES=compiler. 2016-11-16T00:35:29Z Mark Linimon linimon@FreeBSD.org 2016-11-16T00:35:29Z urn:sha1:c92cf8332cf52915fd2f493ccc11c9ca36ab2b00 While here, pet portlint. Approved by: portmgr (tier-2 blanket) 2016-08-16T17:33:56Z Kurt Jaeger pi@FreeBSD.org 2016-08-16T17:33:56Z urn:sha1:760b72d262bacfedba6a6aa644256c5d1142d371 - allows port to build on 32bit/i386 PR: 211881 Submitted by: cyclaero@gmail.com 2016-08-11T11:12:22Z Kurt Jaeger pi@FreeBSD.org 2016-08-11T11:12:22Z urn:sha1:b86d7a843513d60a1b181e012993978b8375bf68 Tools for generating IP based Geo-block-ing and Geo-routing tables in order to configure the system's firewall and/or routing facilities In general, routing is determined by destination IP addresses, and access control by the firewall is established by selectors that can be attrib- uted to incoming and outgoing IP packets, like physical interfaces on which the packets are going, source and target IP addresses, protocol types, port numbers, content types and content, etc. The Geo-location would be just another selector, but this information is not carried explicitly with IP packets, however, it can be obtained using an IP address as a key for looking-up the location in an IP database. Online databases do exist, but these are usually limited to single queries and in addition the look-up in an online database is by far too slow for even thinking about being utilized at the firewall level, where IP packets need to be processed in a microsecond time scale. Therefore, a locally maintained Geo-location database is indispensable in the given respect. The System's own routing and filtering tables can be configured to do these tasks if there is a source of the appropriate data. The ipdbtools(1) are designed to provide this data and to assist managing and using it. WWW: https://cyclaero.github.io/ipdb/ PR: 211744 Submitted by: cyclaero@gmail.com