Hi, if you add your additional dependencies which are not in KDE's flatpak runtime currently, then I guess it won't have any difference for your users. They will either have to download a runtime requiring more space or an app bundle/repo requiring extra space due to QtLocation, QCA and so on. My personal opinion is that we should cover the most needed stuff for most of the KDE/Qt applications, while keep the extra dependencies in application manifests itself, avoiding to make our runtime unnecesarily huge. Anyway, it's not me who takes care currently of KDE/Qt flatpak runtime, so not my decision.
Regards, Jan On pondělí 14. listopadu 2016 12:44:42 CET Matthias Kuhn wrote: > Hi, > > I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was > very happy to see the work on a KDE flatpak repository which already > packages Qt [2]. > > I have recently been looking into a couple of different approaches to > ship app bundles and flatpak sounds like a very interesting one. > > To not duplicate work I would like to ask if there is interest for a > collaboration. In particular, for our needs: > > * We require the QtLocation module. Are there plans for adding this? > I will be happy to share a trivial patch that adds this. > > * We also require other components which are closely related to Qt: > Qt Cryptographic Architecture (QCA), QWT, QScintilla, PyQt5, would > you be interested in integrating them into this repository as well? > > Kind regards > Matthias > > [1] http://qgis.org > [2] https://community.kde.org/Guidelines_and_HOWTOs/Flatpak
