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), part II. The first part covered 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. This adds ports with USES=fortran and ports using Mk/bsd.octave.mk which in turn has USES=fortran. PR: 214965 Reported by: thierry
A lot of KDE Ports share MASTERSITES, LICENSE and so one, as they are released as a bundle upstream, however, there was not really a clean way to share this information. Using these new categories, we can simplify the Makefiles for the diverse KDE ports. At the moment we support the virtual category * kde-kde4 In the future, this will be extended to * kde-frameworks * kde-plasma * kde-applications PR: 213406 Differential Revision: https://reviews.freebsd.org/D7645 Exp-run by : antoine Reviewed by: mat, rakuco Approved by: portmgr (mat), rakuco (mentor)
- Project is hosted on Github now Update math/qalculate to 0.9.9 - Qalculate now uses GTK+3 - Project is hosted on Github now - Take maintainership Bump PORTREVISION on ports that depend upon libqalculate due to shlib increase
Plasma5 ports
At the moment KDE ports use bsd.kde4.mk to handle their dependencies. When
working on the ports for KDE Frameworks and Plasma5 it seemed to be more
reasonable to create a new kde.mk instead of adding an bsd.kde5.mk.
The kde.mk in this review is a stripped down version of the one we are using in
the KDE Test repositories plasma5 branch [1] to only contain the parts relevant
to the current KDE4 ports in the portstree [2].
Changes to the KDE Ports needed by this:
Replace USE_KDE4 by USE_KDE [3]
Add USES=kde:4 [4]
[1] http://src.mouf.net/area51/view/branches/plasma5/KDE/Mk/Uses/kde.mk
[2] The version in the plasma5 branch also handles frameworks/plasma5 and
handles MASTER_SITES via a KDE_DIST variable similar to bsd.qt.mk for Qt
Ports -- I chose to leave this out for now, as the diff is already large
enough.
[3] I chose USE_KDE instead of USE_KDE4, USE_KDE5, USE_KDEX as the version we
want is already specified as argument to kde:<arg>
[4] For KDE Frameworks and Plasma5 ports this would be kde:5
PR: 210667
Approved by: portmgr, mat (mentor), rakuco (mentor)
Reviewed by: mat, rakuco
Differential Revision: https://reviews.freebsd.org/D6961
longer. This is a no-op because KDE4_PREFIX is equal to LOCALBASE Fix up properties for misc/kde4-l10n/files/bsd.l10n.mk to make svn happy. PR: 209014 (partial) Submitted by: myself Approved by: portmgr (bapt) Differential Revision: https://reviews.freebsd.org/D6542
With hat: portmgr Sponsored by: Absolight
Install x11/kdelibs4's headers into include/kde4 instead of include (which
consequently causes several other ports to have their installation paths
changed too).
The idea behind this is to reduce path conflicts between KDE4 ports and the
upcoming KDE Frameworks 5 ports that will be installed into include/KF5. If
we continue installing the KDE4 headers into include/, we can end up in a
situation like this:
c++ [...] -I/usr/local/include -I/usr/local/include/KF5 file.cpp
If the KDE4 and KF5 versions of a port have the same headers, the KDE4 port
will unintentionally be picked up first and the build will fail.
Most of this huge patch is just PORTREVISION bumps, pkg-plist changes and a
few patches to FooConfig.cmake files to make them look into the kde4/
subdirectory in include/.
Changes which don't fit into the above are:
- deskutils/kdepimlibs4: Import an upstream patch to remove some double
semicolons that cause base GCC to fail. They have always been present, but
since the faulty header was referenced via -isystem /usr/local/include
this never caused any problems.
- devel/subversion, devel/subversion18: Update patch-configure. The current
kwallet changes there date back to 2011 (r272490), at a time when the
build could fail when both KDE3 and KDE4 were installed. Replace those
bits with a change I've submitted upstream to use the kde4-config program
to determine where KDE4's headers and libraries are installed instead of
assuming the headers are always in include/.
Once again, huge thanks to Tobias Berner <tcberner@gmail.com> for being the
first one to notice this problem when working on the KDE Frameworks 5 ports,
coming up with the solution and bugging me until I had time to work on this
and ask for the exp-run :-)
PR: 207906 (exp-run)