> This is most likely a problem with the $PATH variable in case of application > bundles, as launching it from the command line > (running /Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader > from the Terminal if default path) seem to > work fine. > I am not sure if there would be an easy way to force the application to use > MacPorts' path when double-clicked.
One option is to make Contents/MacOS/krusader be a shell script that sets the path prior to executing the original binary, renamed in the same directory. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
