(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
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
Details:
- Update to upstream version 9.9.0
- Manpages do not come pre-packaged anymore, hence new
build dependencies to docbook-xsl, libxslt and po4a
in case translations are requested
- Add MANTRANS option to build translated manpages
Detailed log:
- Update to upstream version 9.8.0
- Remove no longer used CONFIGURE_ARGS
- BUILD_DEPENDS on devel/rubygem-rake
- bundled drake is retired
- USE_RUBY is no longer required
- retire custom do-build and do-install targets
Many ports passed ZLIB_CFLAGS="-I/usr/include" ZLIB_LIBS="-L/usr/lib -lz"
which is unsafe at least with lang/gcc* that override some system headers
and have newer libgcc_s.so that our old version in base may not be
forward-compatible with.
Details:
mkvtoolnix shows spurious build issues due to a gcc-internal segfault
on the build cluster on 9.x. However, this is not perfectly
reproducible and on other hardware setups it builds reliably, so we
don't want to mark it broken on 9.x.
Taking maintainership so pkg-fallout won't continue spam the
multimedia@ mailing list.
Details:
- Update to upstream version 9.0.1 (released on 2016-03-28
- Update MASTER_SITES
- Retire CURL OPTION. Rationale: curl is not required for mkvtoolnix
core functionality, but to check for upstream updates. There is little
use for this feature when distributing software via ports / packages.
- Update to 8.5.2.
- WXGTK support has been removed upstream in favour of Qt
- Amend BROKEN message
- Enable verbose build when PACKAGE_BUILDING is set (instead of BATCH)
- Decouple CURL option for online update checks from QT5
- Add NLS option
- Sort plist
PR: based on 204312
Submitted by: yuri@rawbw.com
the now deprecated WXGTK version in the future. If you're currently launching 'mmg'
(the WXGTK GUI) you will get the following notification:
Please note that this program (mkvmerge GUI) is deprecated and will be removed
within one or two releases. It has been superseded by the new MKVToolNix GUI
which should also be included in the same package.
Don't enable this option by default to give current users a notice that future
updates will pull in the Qt5 dependency chain by default. However, users are
encouraged to try the Qt5 version and report bugs.
This new option does not change the current default build of the port and
therefore no PORTREVISION bump is required.
This port was strange in that it not only failed to set the environment,
it was unsetting PREFIX to whatever environment it had. This change sets
the environment in both build and install targets with the exception of
PREFIX. I don't know why that is done, but I maintained that part.
While here, unsuppress the commands so that the build can be logged and
change ";" to "&&" conjunctions which is preferred.
Approved by: blanket
