<table><tr><td style="">davidedmundson created this revision.<br />Herald added a project: Frameworks.<br />Herald added a subscriber: kde-frameworks-devel.<br />davidedmundson requested review of this revision.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D27451">View Revision</a></tr></table><br /><div><strong>REVISION SUMMARY</strong><div><p>This drops the use of kinit as per <a href="https://phabricator.kde.org/T12140" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T12140</a>. Few applications link to<br />
kdeinit correctly and the potential savings that come from library <br />
linking are now negligible.</p>
<p>We use the internal app spawning path for the majority of application<br />
launches anyway via the relatively new KRun::runApplication. There isn't<br />
a need for runService to support a more complex addition path.</p>
<p>It will also simplify any future changes coming to KRun.</p></div></div><br /><div><strong>TEST PLAN</strong><div><p>Opened a file from kicker's recently used selection (which uses this runService)<br />
It opened as normal, with correct startup notifications</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R241 KIO</div></div></div><br /><div><strong>BRANCH</strong><div><div>master</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D27451">https://phabricator.kde.org/D27451</a></div></div><br /><div><strong>AFFECTED FILES</strong><div><div>src/widgets/krun.cpp</div></div></div><br /><div><strong>To: </strong>davidedmundson<br /><strong>Cc: </strong>kde-frameworks-devel, LeGast00n, cblack, GB_2, michaelh, ngraham, bruns<br /></div>