Review Request 116928: Default to not launching kded

[Sebastian Kügler]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116928/#review53526
-----------------------------------------------------------


Can you make sure that kded is launched in Plasma sessions? Just removing it and going "it can be started" is not good enough, we need it, we know that, and we don't want to introduce regressions in the workspace.

- Sebastian Kügler


On March 20, 2014, 3:04 p.m., Alex Merry wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/116928/
> -----------------------------------------------------------
> 
> (Updated March 20, 2014, 3:04 p.m.)
> 
> 
> Review request for KDE Frameworks.
> 
> 
> Repository: kinit
> 
> 
> Description
> -------
> 
> Default to not launching kded
> 
> It can be autolaunched as required.  Plasma sessions can use the --kded
> argument to always start it.
> 
> Allow both --no-fork and --nofork arguments to kdeinit
> 
> Different platforms have had different versions of this argument, and
> KUniqueApplication used --nofork.  The help text standardises on
> --no-fork, as that matches the other arguments, but both versions are
> accepted.
> 
> 
> Diffs
> -----
> 
>   src/kdeinit/kinit.cpp 82d570c4453cf083e525125edd448b97d8d11bd3 
> 
> Diff: https://git.reviewboard.kde.org/r/116928/diff/
> 
> 
> Testing
> -------
> 
> Builds, installs.  `kdeinit5` does not launch kded5, while `kdeinit5 --kded` does.
> 
> 
> Thanks,
> 
> Alex Merry
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140320/986c9a70/attachment-0001.html>