Number of commits found: 29

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

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

Bump PORTREVISION for ports depending on the canonical version of GCC
(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

Chase a bunch of failures after libsigc++20 update

New libsigc++20 requires c++11 (it exposes c++11) so explicitly use -std=c++11
where needed.
Mark as broken a bunch of ports which are not c++11 compatible

Remove ${PORTSDIR}/ from dependencies, Mk and categories a, b, and c.

With hat:	portmgr
Sponsored by:	Absolight

Reduce unnecessary bsd.port.options.mk inclusions by using OPTIONS helpers.

For liborange, reverse the logic, as I'm pretty sure the OPTIONS were being
used to disable the selected options.

Approved by:	portmgr (blanket)

- Switch to USES=libtool, drop .la files

Approved by:	portmgr blanket

Remove trailing whitespaces from category archivers

According to the Porter's Handbook (5.12.2.3.) default options must be added to
OPTIONS_DEFINE. This policy has been implemented only recently that's why we
have many ports violating this policy.

This patch adds the default options specified in the Porter's Handbook to
OPTIONS_DEFINE where they are being used. Ports maintained by
gnome@FreeBSD.org, kde@FreeBSD.org and x11@FreeBSD.org have been excluded.

Approved by:    portmgr (bapt)

Part 1 at removing now useless FETCH_ARGS redifition

Update to 0.4
Support STAGE

PR:		ports/183569
Submitted by:	Nicolas Raspail
Approved by:	swills (mentor)

Add NO_STAGE all over the place in preparation for the staging support (cat:
archivers)

Fix build without libstdc++

- Update to 0.3 [1]
- Remove USE_GCC (builds with clang) [1]
- Add LICENSE (GPLv2)

This is a new upstream, the original is dead.

PR:		ports/179029
Submitted by:	Herbert J. Skuhra <h.skuhra@gmail.com>
Approved by:	culot (mentor), maintainer

- Use gcc for now (does not compile with clang)

Upstream seems inactive for about 7 years

PR:		ports/178989
Submitted by:	wg (myself)
Approved by:	culot (mentor)

Finish converting the whole ports tree to USES=pkgconfig

* Update the glib to 2.34.3 and gtk20 to 2.24.17 and gtk30 to 3.6.4 which
  are the latest stable releases.
* Update vala to the newest stable release 0.18.1, also update a few ports
  in the gtk/gnome stack.
* The c++ bindings ports for glib, atk, gconf, etc, have now USE_GNOME toggles.
* Remove pkg-config run depends from glib20 and freetype2. This doesn't
  eliminate pkg-config run dependency completely, a second phase is needed
  and is planned.
* Support for .:run. and .:build. for USE_GNOME components was added.
  Currently only libxml2 and libxslt support this mechanism.
* Updates of the telepathy stack and empathy.
* Trim makefile headers, convert ports to new options, trim off library
  versions for some ports.
* Fix other ports so they build with the new glib version.

Thanks to miwi and crees for helping out with some exp-runs.
Approved by:	portmgr (miwi & bapt)
Obtained from:	gnome team repo

- Update patches required by nzbget

PR:		ports/175846
Submitted by:	Mark Felder <feld@feld.me>
Approved by:	Jeff Burchell <toxic@doobie.com> (maintainer)

For a number of ports in archives category, trim the header and drop leading
indefinite article from COMMENT line; also fix few noticed styles bugs while
I am here.

Convert to new options framework

PR:		ports/173810
Submitted by:	Chris Petrik <c.petrik.sosa@gmail.com>
Approved by:	Jeff Burchell <toxic@doobie.com>
Feature safe:	yes

- Remove WITH_FBSD10_FIX, is no longer needed

- Fix build on FreeBSD 10

- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead

PR:             157936
Submitted by:   myself
Exp-runs by:    pav
Approved by:    pav

- DISTNAME= ${PORTNAME}-${PORTVERSION} is the default and not needed.

PR:             ports/153292
Submitted by:   myself (pgollucci)
Tested by:      -exp run by pav
Approved by:    portmgr (pav)

- Includes two patches

        * a bugfix that closes a memory leak triggered by corrupted PAR2 files.
          That fix is included in some linux vendors' libpar2 packages, and is
          well-tested.
        * The other adds additional functionality: a method to cancel a file
          repair in progress. This patch can be disabled through a config
option.
          It is enabled by default because the only application in the ports
tree
          that links against libpar2 is news/nzbget. Nzbget makes use of this
          functionality if it is available.

PR:             146125
Submitted by:   Jeff Burchell <toxic@doobie.com> (maintainer)

- Switch SourceForge ports to the new File Release System: categories starting
with A

Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.

To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.

To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.

Changes to Mk/*:
 - Add runtime detection magic in bsd.port.mk

(Only the first 15 lines of the commit message are shown above )

Fix NOPORTDOCS related issues
Noticed by: ionbot

[NEW PORT] archivers/libpar2 Reusable library for manipulating par2 files

        Libpar2 is a library for creating and using PAR2 files to detect
        damage in data files and repair them if necessary. It can be used with
        any kind of file. Par files are especially popular on Usenet.

        Libpar2 is extracted from par2cmdline, and distributed separately.

        WWW: http://parchive.sourceforge.net/

PR:             ports/126578
Submitted by:   Jeff Burchell <toxic@doobie.com>

Number of commits found: 29

13 vulnerabilities affecting 158 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2018-12-12 10:25:27