Proudly brought to you by the KDE on FreeBSD team. We're sorry to ship two
KDE updates in just a few days, but the work on 4.10.5 was very light
compared to 4.10.4 so it was ready much faster.
The release announcement can be found in [1].
[1] http://www.kde.org/announcements/announce-4.10.5.php
The biggest news for us on FreeBSD is that the Ruby bindings should work
with Ruby 1.9 now.
I will probably add a note to UPDATING later about this, but as avilla@
pointed out, the clang support we mentioned that was improved in 4.10.4
requires a rebuild of the ports that depend on kdelibs4. Most of them are
covered by this update, but those which are not part of the Software
Compilation need to be rebuilt manually to make sure the previous issues
(proper symbol visibility being the most annoying of them) are solved.
With commits from avilla@, makc@, rakuco@ and Schaich Alonso.
The upstream announcement can be found in [1].
[1] http://www.kde.org/announcements/announce-4.10.4.php
clang support should be more stable now, with clang being recognized by
kdelibs4 and being passed the correct flags to build other ports.
Additionally, all ports being committed have been verified to build with
-CURRENT's clang 3.3 on an amd64 tinderbox (special thanks go to swills@ for
providing it).
Work on the newly-released 4.10.5 will begin shortly.
- kdegames4 port has been split.
- kdeutils4-printer-applet and system-config-printer-kde have been
replaced by print/kde4-print-manager.
- Recover misc/kde4-l10n-mr from attic.
- New USE_KDE4 components: kactivities, libkdegames, nepomuk-core,
and nepomuk-widgets.
- Provide sharedmime component with magic: ports don't need to
run update-mime-database themselves now.
- Switch some ports to out-of-source build.
- Update port comments.
- Adjust dependence on Qt4 components.
- x11/kde4 installs modern kdepim4 now.
- Remove redundant aspell and hspell from kdelibs4, both
can be enabled in textproc/enchant if needed.
- Remove stale bits from bsd.kde4.mk
The area51 repository features commits by Schaich Alonso and myself.
Contributors:
- Tobias Berner
- Don't set CMAKE_BUILD_TYPE for debug builds (cmake.mk already handles it)
- Don't set WITH_DEBUG for unstable branch (KDE4_BRANCH)
- Remove now useless KDE4_BUILDENV
KDE SC ports:
- Chase KDE4_BUILDENV removal: replace 'KDE4_BUILDENV= yes' with
'USES= cmake:outsource' and add USE_LDCONFIG if needed
- kdebindings ports have been renamed to match upstream.
- kdemultimedia and kdenetwork have been split.
- New port games/pairs added.
- Trim Makefile header
- Convert to new option framework
- New USE_KDE4 components: libkcddb, libkcompactdisc
- Update:
databases/akonadi to 1.9.0
devel/grantlee to 0.3.0
textproc/rasqal to 0.9.30
textproc/redland-bindings to 1.0.16.1
textproc/soprano to 2.9.0
x11-toolkits/attica to 0.4.1
The area51 repository features commits by Schaich Alonso, avilla, dbn,
jhale, makc and rakuco.
Contributors:
- Oleg Sidorkin
- Tobias Berner
- Kurt Jaeger
- Update textproc/clucene to 2.3.3.4. Note this version is required by
recent LibreOffice.
- Remove textproc/clucene-contrib because it is now integrated into
textproc/clucene. [2]
- Mark textproc/p5-Lucene as broken. There is no dependent port and it was
only written for obsolete Lucene 0.9.x API. [3]
- Update deskutils/kdepim4 and deskutils/strigi to build with the new
CLucene port. [4]
- Update misc/bibletime and misc/sword to use new CLucene 2.3.x API. [5]
Approved by: clsung (maintainer timeout) [1]
Approved by: tj (maintainer) [2]
Approved by: perl [3]
Approved by: kde [4]
Approved by: tabthorpe (maintainer timeout) [5]
Obtained from: The SWORD Project [5]
devel/libinotify doesn't support yet some of the events used by the
code, so we can't add it as a dependency, and we need to disable the
checks.
PR: 170209
the authors intended by adding:
USE_AUTOTOOLS= libtool
USE_GNOME= ltverhack
to security/libassuan/Makefile.
Update the libassuan shared library version number and/or bump
PORTREVISION in the dependent ports.
Requested by: ale
Feature safe: yes
Unfortunately version 2.0.0 is largely incompatible with version 1.x, so it
is necessary to have a stopgap measure while ports that depend on libassuan
can be updated. In conversation with the maintainers of the dependent ports
it was originally considered ideal to prepare updates for the ports first,
then upgrade everything to libassuan 2.x en masse. Since no action has
arisen on that front, go with plan B:
Copy security/libassuan to security/libassuan-1, and update the dependent
ports accordingly. Because this is (intended to be) a _temporary_ measure,
and because no updates for libassuan 1.x are anticipated, and because the
hope is that it can be removed sooner rather than later, it's a copy instead
of a repocopy.
