kdebase4 @4.6.0 Applications not available on console after installing

[johnrizzo1@…]

The traditional applications such as kate, etc that are a part of the traditional source are not installed in any location available on the command line but rather are only available as commands listed in /Applications/MacPorts/KDE.

While I think listing them in that location is good so that they can be found using traditional "Mac" methods not having the commands that come with the package is confusing to users familiar with the application on other systems. In the more serious case things such as making EDITOR="kate -b" doesn't work on a mac as it would on other unix systems with KDE installed.

[jmr@…]

Please remember to cc the maintainers.

[snc@…]

kwrite is part of kdebase4

[johnrizzo1@…]

Replying to jmr@…:

Please remember to cc the maintainers.

Thanks. This was my first submission and I didn't realize that had to be done manually. :)

[snc@…]

I'll explore this in the just-released 4.6.1.

[snc@…]

From what I can see in the instance of Kate, they've provided a kate.shell program inside the application bundle that should suffice in launching the program from the command line. Unfortunately, it is populated with build directory paths: perhaps michaelld@ can provide inside on this based on how the portgroup and cmake are setup.

Even if the paths are corrected, this is not consistent behavior across all programs provided by KDE and needs to be addressed by KDE.

Example ktesnippets_editor.shell script:

DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kate/kate/work/build/lib/./:/opt/local/lib${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH} "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kate/kate/work/build/kate/plugins/snippets_tng/editor/ktesnippets_editor.app/Contents/MacOS/ktesnippets_editor" "$@"

PS kate is now its own package.

[snc@…]

Due to the enormous quantity of applications in the KDE suite, this is an issue for upstream (​bugs.kde.org).