T10812: KDE Applications

Luigi Toscano noreply at phabricator.kde.org
Thu Apr 18 23:43:52 BST 2019

ltoscano added a comment.

  In T10812#182252 <https://phabricator.kde.org/T10812#182252>, @cfeck wrote:
  > Yes, we have been trying hard, but did we succeed? Would someone just stop using Okular, because it is shipped with the Plasma bundle instead of the KDE Applications bundle?
  I fear it will happen, yes. Moreover, Plasma bits tend to update their dependecies on base libraries (Qt and Frameworks) at a faster pace than most of the other components. But more important than that it's the branding issue (which why I advocate a change of the name of the bundle).
  > Also, does "Discover" or "Bluedevil" really only work under Plasma?
  That's what the Plasma team decided, and they can decide otherwise. They decided (with reasons) that those components are tightly integrated with the rest of Plasma. This can change, of course; other components were moved out of Plasma over time.
  The discussion about LTS applications it's totally different. No one forces us to provide LTS releases, and from a resource point of view it does not make much sense: most of the applications per of the bundle are independent enough from each other and they don't bump their requirements frequently, so they could be updated by distributions should their policy allow that. But many of them can provide semi-official repositories with updates.
  Talking about CentOS, the direction there is clear: flatpak.


To: ngraham, ltoscano
Cc: ltoscano, cfeck, aacid, #yakuake, #okular, #dolphin, #kate, #spectacle, #konsole, #gwenview, #kde_pim, #kde_games, #kde_applications, ngraham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/konsole-devel/attachments/20190418/12e0fd7f/attachment-0001.html>

More information about the konsole-devel mailing list