Problems of KDE software on MacPorts

Why these pages?

When software is ported from one hardware or operating-system environment to another, problems arise that are nobody's fault. The original software writers can try their best to avoid such problems, but they cannot be expected to foresee every issue. These pages are a place where issues of KDE software on MacPorts can be gathered together for easy visibility and people from KDE and MacPorts can co-operate to narrow each issue down to a point where it can be assigned to a specific area on the KDE Bugtracking System or the MacPorts Ticket System for action. Also, co-operation is needed to set up a continuous testing system, in the longer term, to minimize problems in the future.

These pages were initiated by ​this post on KDE-MAC and a PM discussion regarding ​Randa Meetings participation of MacPorts developers.

Special maintainer/developer information - which is not covered in the KDE wiki page - could also be gathered here.

---

Tickets for specific KDE software issues

Information regarding specific tickets has been moved to a dedicated page.

All other tickets of category "kde4" can be listed in one big table. (Be aware that the generation of this table needs a few seconds on MacPorts' trac.)

New version 4.13 of KDE applications

This is the ​release schedule for the 4.13.x versions. However, MacPorts' KDE version is kept at 4.12.x until 4.13.x has stabilised somewhat.

There were discussions on KDE-MAC and KDE-DEVEL about

• the upcoming ​replacement of nepomuk by baloo (see also the list of ​softwares ported to baloo) and
• the options to disable baloo were discussed ​here and ​there so that there is no interference with OSX' Spotlight

If you want to support the transition to KDE 4.13.3, please:

• check out branch 'KDE4.13' of the ​MacPorts tree distributed via our macports-kde git repository
• and perhaps add it as a ​local MacPorts tree to your (test) system
• find an up-to-date list of problems for some KDE software ports kept in ​dports/kde/TODO.txt.

Report any issues found on ​KDE-MAC or ​MacPorts-Devel mailing lists.

Continuous Integration of KDE software

KDE's developers are running a ​Jenkins-based CI system for the most of the KDE software. While this is already fully functioning for Linux a similar Windows-CI system is in a similar state to the idea of a CI system for KDE application on Mac(ports).

There is also a set of ​code-vetting software called English Breakfast Network (EBN, for short) which supports all developers in writing cleaner code and documentation.

The KDE community has plans to ​introduce CI of KDE software also on OSX. Further details can be found on a dedicated KDE/MacPorts CI page, while the current status of a OSX/CI system based on MacPorts can be checkout out here.

Qt5 and KF5

The new Qt5 eventually lead to the new ​KDE Frameworks.

As tracked in #37331 is was possible to create a portfile for qt5-mac. This means that we can soon start adding those frameworks as new ports.

---

Additional information

• MacPorts-Wiki
• KDE - Installing KDE applications with MacPorts
• ​KDE Community wiki for Mac
• ​KDE Techbase Wiki: Installing a development environment using MacPorts (somewhat outdated, still needs to be tested with current versions of OSX and KDE software)
• ​KDE Applications/Cross Platform Issues page on the "KDE Community Wiki"

---

Other resources

• ​KDE-MAC mailing list
• ​Git repository of a Dedicated MacPorts tree for tests of KDE software on "KDE Projects playground" which also contains helpful ​environment and bash files for MacPorts users and port maintainers
• ​Ian's git repository dedicated to "Fixes for KDE problems that occur on Apple OS X"
• ​kde-mac group on KDE's ReviewBoard