This lets it get launched with KIO::ApplicationLauncherJob. It'ss still
hidden from the user by setting NoDisplay=true on it, because it's kind
of more of an internal utility than a user-facing app.

CCBUG: 464668

We have deprecated API leaking in from KService

master is for Qt6-based development now

Qt5 development continues in the 'kf5' branch

master is Qt6 now

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

There's not really an alternative, this is not supported by KNS, the
only alternative is to have the browser showing it or not then just
cancel it.

This changes the current behaviour so we include the link in the message
so it can be opened but otherwise just issues an error message and
proceeds.

This helps because:
- we don't keep the process blocked waiting for an answer
- we always error out, not only when the user decides to see it in the
browser
- we don't lie to the users making them think there's a choice

More often than not, a question will be about an entry. This is relevant
information about the question. Include the entry in the question so the
client can relate it to e.g. a transaction, as needed by Discover.

CCBUG: 460136

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

The flag is not set during static builds. Thus we need to set the compile definition manually.

BUG: 459125