Guidelines and HOWTOs/Flatpak: Difference between revisions

From KDE Community Wiki
m (Mention new Userbase page)
 
(22 intermediate revisions by 14 users not shown)
Line 1: Line 1:
Flatpak is a solution for creating sandboxed software builds for GNU/Linux systems. You can find more information [http://flatpak.org/ here].
The development information of this page has been moved [https://develop.kde.org/docs/build/flatpak/ here].


{{ Warning | Do NOT use this in production, it's work in progress and it doesn't enable important safety features. It might also eat your pet or first-born.}}
The usage information of this page has been moved [https://userbase.kde.org/Tutorials/Flatpak here].
 
= Applications =
At the moment we are building nightlies of most of our applications. It has the master version of the applications, so expect some unstable development quirks.
On the bright side, if you find one, you get to tell the developers so they can fix it!
 
Here's how to install an application from the terminal:
<syntaxhighlight lang="bash">
flatpak remote-add kderuntime --from http://distribute.kde.org/kderuntime.flatpakrepo
flatpak remote-add kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo
flatpak install kdeapps org.kde.okular
</syntaxhighlight>
 
Or just open the flatpakrepo files with Discover or your otherwise favorite software center:
* https://distribute.kde.org/kderuntime.flatpakrepo
* https://distribute.kde.org/kdeapps.flatpakrepo
 
= Qt and KF5 Runtime =
We provide a runtime with Qt and all KDE Frameworks 5 (except for the 4th tier) to make sure it's easily adaptable for any KDE Application and possibly most Qt-based applications as well.
 
This runtime can be added by following these instructions:
<syntaxhighlight lang="bash">
flatpak remote-add kderuntime --from http://distribute.kde.org/kderuntime.flatpakrepo
flatpak install kderuntime org.kde.Platform//5.9
flatpak install kderuntime org.kde.Sdk//5.9
</syntaxhighlight>
 
{{ Note | All flatpak commands (such as <code>remote-add</code> and <code>install</code>) accept a <code>--user</code> option to install things at the user level, without being prompted for the sudo password every time. }}
 
= Compile your application =
 
Now you get to compile your favorite application. If you want to see how it's done, you can see some of the ones that have already been built. You can find it [https://cgit.kde.org/flatpak-kde-applications.git/tree/ here].
 
To compile an applications, you should create a json file similar to the ones in the previous link. Then you'd just need to trigger the build and get it into a repository. For testing, I recommend just creating a local one (to publish an rsync will be required).
 
<syntaxhighlight lang="bash">
mkdir app repo
flatpak-builder --ccache --repo=repo --subject="Build of AWESOMEAPP `date`" app org.kde.AWESOMEAPP.json
</syntaxhighlight>
 
This will do everything required and create a repository in ./repo. To test the application we add the repository (called remotes), we install the application and then we run it:
<syntaxhighlight lang="bash">
flatpak remote-add awesomeapp repo --no-gpg-verify
flatpak install awesomeapp org.kde.AWESOMEAPP
flatpak run org.kde.AWESOMEAPP
</syntaxhighlight>
 
Now you will see that some things don't work and you'll have the privilege to start fixing things!
 
= Contribute! =
In the following repositories you'll find the code in charge of packaging the runtime (Qt 5 and KF5) and then several (but not all, yet) KDE Applications.
* Runtime: https://phabricator.kde.org/source/flatpak-kde-runtime/
* Applications: https://phabricator.kde.org/source/flatpak-kde-applications/
* Our XDG portals: https://phabricator.kde.org/source/xdg-desktop-portal-kde/
 
= Flatpak portals =
Portals are high-level session bus APIs that provide selective access to resources to sandboxed applications. The implicit expectation of portals is that the user will always be involved in granting or rejecting a portal request, thus most portal APIs will lead to user interaction in the form of dialogs.
 
Since such dialogs must fit into the user experience of the desktop shell, the portal APIs are implemented by a generic frontend called [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] which calls out to desktop-specific implementations that provide the actual UI. The bus name through which the portal APIs are available is org.freedesktop.portal.Desktop, with the object path /org/freedesktop/portal/desktop implementing the various portal interfaces.
{{ Note | You can find more information about flatpak portals [https://github.com/flatpak/flatpak/wiki/Portals here]. }}
 
== KDE implementation of portals ==
KDE backend for flatpak portals is called [https://cgit.kde.org/xdg-desktop-portal-kde.git/ xdg-desktop-portal-kde] and is now part of Plasma releases (starting with Plasma 5.10). Currently it supports most of the portals. To make Qt applications use or call portals frontend in sandbox we developed a Qt platform plugin which is now part of our runtimes. All you need to make your app use the plugin is to pass '''-platform flatpak''' parameter, or set QT_QPA_PLATFORM variable to flatpak. If you want to test KDE flatpak portals, you can use this [https://github.com/grulja/flatpak-portal-test-kde simple test app].
 
= Styles and integration with other desktops =
We are aware that not everyone is using KDE/Qt applications in Plasma desktop. For this flatpak comes with extensions, where you specify a directory (with themes, icons) where third-party is allowed to install additional stuff as an addition to what we have in our runtimes. At this moment we have added support for Gnome in form of adwaita icons and adwaita-qt style. All you need to is install following extensions using commands below:
<syntaxhighlight lang="bash">
flatpak install kderuntime org.freedesktop.Platform.Icontheme.Adwaita
flatpak install kderuntime org.kde.KStyle.Adwaita
flatpak install kderuntime org.kde.PlatformTheme.QGnomePlatform
</syntaxhighlight>

Latest revision as of 13:42, 6 January 2023

The development information of this page has been moved here.

The usage information of this page has been moved here.