© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
(In reply to Forest from comment #15)
> (In reply to Bernd Steinhauser from comment #14)
>
> > I'd say the better fix would be to [...]
> > instead provide a systemd user unit that starts kdeconnect.
>
> Not everyone uses, or even wants, systemd. (Or linux, for that matter.)
> Please don't add dependencies on it.
>
Ah, not this again …
But ok, let's skip the useless discussion.
1. Plasma is moving towards systemd user units already, as I wrote above. It's the default method to startup Plasma these days. So it kind of makes sense to go a similar path with kdeconnect. (Yes, you can use kdeconnect outside of Plasma, but just about every other DE is also moving towards systemd support/
2. A systemd service unit does *not* introduce a dependency on systemd. It's merely an instruction for systemd to tell it what to do when this service is enabled and/or started. If you don't use systemd, it's just a small text file that will sit on your computer unused. You can of course also choose not to install it. I guess though that any sensible distribution would install it.
3. Just like with Plasma, you can still use the old, flawed, method to start it up. XDG autostart will not go anywhere. If you're unhappy with the old method, feel free to create an alternative approach that does not use systemd. Nothing holding you back there. Just don't expect somebody else to drop a better solution just because you don't like it. systemd is the current standard for Linux and for that reason alone it makes sense to support it. Especially, since this support comes at advantages, which is why everybody is using it.
> KDE already has way to manage things like this, with the Background Services
> and Autostart control panels.
>
I'd expect this to move to systemd as well. There is no reason to maintain a second, system to manage background services and autostart functionality, when you're already using a better one that even can be used across DEs.
Likely, it will remain though for quite some time, for compatibility reasons and because it takes will and time to do the changes.
Thus, in the future (+5 years?) it might go the way of the dodo, we'll see.