- Address comments.
Moving this to GitLab: https://invent.kde.org/frameworks/kio/-/merge_requests/143
Fri, Sep 18
Thu, Sep 17
Moved to GitLab: https://invent.kde.org/wrobelda/vcpkg/-/milestones
Moved to GitLab: https://invent.kde.org/wrobelda/vcpkg/-/issues/1
Moved to GitLab: https://invent.kde.org/wrobelda/vcpkg/-/issues/2
Moved to GitLab: https://invent.kde.org/wrobelda/vcpkg/-/issues/3
Moved to GitLab: https://invent.kde.org/wrobelda/vcpkg/-/issues/4
dolphin plugins that solely target developers
By far not everyone of our users is an expert, and I don't see the numbers to back this up as a huge problem yet. There sure has been the odd forum thread about missing stuff, but through our KDE Wiki it is common knowledge that users are supposed to use the plasma-meta package and that settles it real quick. Is it really beginners who randomly install the minimal plasma-desktop package (if they do, why?) rather than following the distro's Wiki, or is it the tinkerer who doesn't own up to hunting for features manually after going the minimal route? How many distros get it actually wrong, can it be improved by adding RUNTIME infos to cmake? Where are those bug reports you see coming from? Those are the questions before establishing this as a problem we need to fix by lumping repositories together. And that would change it for something like Arch where binary packages are not often being split, but not for others like Debian where the amount of binary packages may not even change except where they pull their sources from.
- More const QString.
Wed, Sep 16
I agree with moving the runners, but it is also planned to introduce some new APIs so that the Kate/Konsole profiles runners can be replaced and are provided within the Kate/Konsole apps themselves. For the remaining runners it makes totally sense.
I don't try to nanny our users into accepting all those extra dependencies.
From me also a -1, mostly because of the dependency tree. Stuff like ffmpeg and Samba have a *huge* dependency tree.
stuff in *-extras is not core functionality but provides additional features that one may or may not want to use
Distros can fail to pre-install them in their Plasma packaging, leading to users missing content and having a sub-optimal user experience
Sure, distros make mistakes too, but that kind of mistake is easy to address downstream
Users of DIY distros like Arch or Debian can fail to install them and wind up missing content and having a sub-optimal user experience
That's the price you needs to pay for using such a distro. You need to think about what to install. Following the logic of why some people prefer this kind of distro one can argue that some people do not install these extra packages on purpose.
Reduces the clarity of the software's status: Is this stuff core functionality or not? On the one hand, it's hosted on KDE infrastructure and tracked on KDE's Bugzilla. But on the other hand, it's possible to not install it
How is merging it clarifying anything? Right now the status is pretty clear IMO: stuff in *-extras is not core functionality but provides additional features that one may or may not want to use
On the flip side, I see no major advantages to having stuff split into these extra repos.
For a framework like KIO I made my point above. A similar point can be made for Plasma too. Plasma is used as a base for various embedded products (Plasma Mobile, Mycroft, Plasma Bigscreen, kiosk deployments. I've also seen kwin used as a standalone window manager in commercial products). For these kinds of projects it is beneficial to be able to deploy a core-only version of our product since stuff like installation size does matter.
Alternatively, do you see a better place to merge kio-etras?
No, but I don't see a pressing need to merge it anywhere either
increases work for KDE's release team and distro packagers to have more packages to tar, package, update, manage, etc
-1 on merging kio-extras into kio. For frameworks we need to keep an eye on the dependency tree and kio-extras has quite a number of additional dependencies (phonon, samba, libssh, mtp, kdsoap etc) and the features that kio-extras provides are usually. I don't want my app to depend on all of that just to be able to use ApplicationLauncherJob et al
Tue, Sep 15
We could kill it regardless of regressions in performance. That could simplify plasma significantly
Mon, Sep 14
I need help from someone with good understanding of Solid to continue.