This drops the use of kinit as per T12140. Few applications link to
kdeinit correctly and the potential savings that come from library
linking are now negligible.
We use the internal app spawning path for the majority of application
launches anyway via the relatively new KRun::runApplication. There isn't
a need for runService to support a more complex addition path.
It will also simplify any future changes coming to KRun.
Opened a file from kicker's recently used selection (which uses this runService)
It opened as normal, with correct startup notifications
| No Linters Available |
| No Unit Test Coverage |
| Buildable 22560 | |
| Build 22578: arc lint + arc unit |
For the record, it LGTM and I'm glad to see this point discussing during the sprint coming through. :-)
This makes runService and runApplication almost the same, right?
KRecentDocument::add seems missing in runApplication, but that's a bug, so one could just call the other?
This makes runService and runApplication almost the same, right?
Yeah, that was the goal.
KRecentDocument::add seems missing in runApplication, but that's a bug
If that is a bug, then we may as well share the implementation. I'll do that.