IMO it should just check for both and prefer qdbus-qt5 if available.

In D15606#328493, @fvogt wrote:

IMO it should just check for both and prefer qdbus-qt5 if available.

Yes, that was my starting patch, but then I got unsure about the great picture.
If going this route, any shell script wizard proposal how to change checkToolsInPath in kdevplatform_shell_environment.sh to check for both variants, without adding too much boilerplate code?
kdevelop! I had changed to if ! [ "$(which qdbus-qt5)$(which qdbus)" ]; then which should work fine, no?

In D15606#328495, @kossebau wrote:

In D15606#328493, @fvogt wrote:

IMO it should just check for both and prefer qdbus-qt5 if available.

Yes, that was my starting patch, but then I got unsure about the great picture.
If going this route, any shell script wizard proposal how to change checkToolsInPath in kdevplatform_shell_environment.sh to check for both variants, without adding too much boilerplate code?

What about this:

qdbus_exe=$(which qdbus-qt5 qdbus 2>/dev/null | head -n1)

if [ -z "${qdbus_exe}" ]; then checkToolsInPath qdbus-qt5; fi

$qdbus_exe $KDEV_DBUS_ID etc.

`kdevelop!` I had changed to `if ! [ "$(which qdbus-qt5)$(which qdbus)" ]; then` which should work fine, no?

Looks fine to me, but doesn't the other script check for its presence already?

In D15606#328516, @fvogt wrote:

In D15606#328495, @kossebau wrote:

In D15606#328493, @fvogt wrote:

IMO it should just check for both and prefer qdbus-qt5 if available.

Yes, that was my starting patch, but then I got unsure about the great picture.
If going this route, any shell script wizard proposal how to change checkToolsInPath in kdevplatform_shell_environment.sh to check for both variants, without adding too much boilerplate code?

What about this:

qdbus_exe=$(which qdbus-qt5 qdbus 2>/dev/null | head -n1)

if [ -z "${qdbus_exe}" ]; then checkToolsInPath qdbus-qt5; fi

$qdbus_exe $KDEV_DBUS_ID etc.

Thanks. Small issue I have with this that it would result in the error message only talking about qdbus-qt5, which might be a name not making sense on some platforms. Instead proposing in the updated patch to use some explicit custom code, with custom warning.

`kdevelop!` I had changed to `if ! [ "$(which qdbus-qt5)$(which qdbus)" ]; then` which should work fine, no?

Looks fine to me, but doesn't the other script check for its presence already?

Not exactly sure why this is, so left that aspect untouched for now.