September 05, 2019.
Today KDE released the first stability update for KDE Applications 19.08. This
release contains only bugfixes and translation updates, providing a safe and
pleasant update for everyone.
More than twenty recorded bugfixes include improvements to Kontact, Dolphin,
Kdenlive, Konsole, Step, among others.
Improvements include:
* Several regressions in Konsole's tab handling have been fixed
* Dolphin again starts correctly when in split-view mode
* Deleting a soft body in the Step physics simulator no longer causes a crash
You can find the full list of changes here:
https://kde.org/announcements/fulllog_applications-aether.php?version=19.08.1
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
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, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
July 11, 2019.
Today KDE released the third stability update for KDE Applications 19.04. This
release contains only bugfixes and translation updates, providing a safe and
pleasant update for everyone.
Over sixty recorded bugfixes include improvements to Kontact, Ark, Cantor, JuK,
K3b, Kdenlive, KTouch, Okular, Umbrello, among others.
Improvements include:
* Konqueror and Kontact no longer crash on exit with QtWebEngine 5.13
* Cutting groups with compositions no longer crashes the Kdenlive video editor
* The Python importer in Umbrello UML designer now handles parameters with default arguments
Changelog:
https://kde.org/announcements/fulllog_applications-aether.php?version=19.04.3
a symbol matches multiple clauses the last one takes precedence. If the
catch-all is last it captures everything. In the case of Qt5 libraries
this caused all symbols to have a Qt_5 label while some should have
Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the
catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
in the weak wrapper resolves to the weak wrapper itself creating an infinite
call loop that overflows the stack and causes a crash. Some of the
allocation functions are variants of C++ new and delete and it probably
depends on the compiler whether these variants are used in other parts of
Qt5Webengine.
Remove the weak wrappers (make them Linux specific). This isn't binary
compatible but we are already breaking that with the changes to the symbol
versions.
[1] 5c2cbfccf9
[2] 2ed5054e3a
[3] 009f5ebb4b
Bump all ports that depend on Qt5.
PR: 234070
Exp-run by: antoine
Approved by: kde (adridg)
Release Announcement:
https://www.kde.org/announcements/announce-applications-18.12.1.php
Today KDE released the first stability update for KDE Applications 18.12.
This release contains only bugfixes and translation updates, providing a
safe and pleasant update for everyone.
About 20 recorded bugfixes include improvements to Kontact, Cantor, Dolphin,
JuK, Kdenlive, Konsole, Okular, among others.
Improvements include:
* Akregator now works with WebEngine from Qt 5.11 or newer
* Sorting columns in the JuK music player has been fixed
* Konsole renders box-drawing characters correctly again
You can find the full list of changes here:
https://www.kde.org/announcements/fulllog_applications-aether.php?version=18.12.1
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
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
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
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: →https://reviews.freebsd.org/D15540
The Boost::Python bindings are searched for in a bunch of 2.x versions,
and no 3.x versions. Force the use of Python 2.7. No PORTREVISION bump,
since the port doesn't change -- if you had Python 3 as default before,
kig just didn't build.
Approved by: tcberner (mentor, implicit)
This is another bit of fallout from the change in CMake 3.11.0 which
respects CMAKE_REQUIRED_LIBRARIES in check_headers. It took a while
for us to be able to reproduce the problem, though.
Submitted by: tcberner
Reported by: pkg-fallout
Reviewed by: adridg
Approved by: tcberner (mentor, implicit)
* math/analitza
* math/cantor
* math/kalgebra
* math/kbruch
* math/kcalc
* math/kig
* math/kmplot
* math/rocs
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
In order to make room for the up-to-date version of the KDE Desktop and its
applications move the KDE Application ports based on Qt4.
PR: 225992
Exp-run by: antoine
Reviewed by: rakuco, adridg
Differential Revision: https://reviews.freebsd.org/D14413
This is done for
* consistency,
* and to simplify the import of the newer KDE Plasma5 desktop and KDE applications
Bumps the dependencies.
Reviewed by: adridg
Differential Revision: https://reviews.freebsd.org/D12979
(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
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)
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
