It'd be nice if there were a direct download + install for flatpak applications. Either licking on the URL in Firefox causes GNOME Software to autolaunch and do whatever needs to be done (find and install runtimes as well as the application); or maybe an included webextension for Firefox that can do the installation.
At the moment I'm confused about --system vs --user installation locations. Somehow I have some things that are system and others are user. This is relevant because a system domain installation means it's the rootfs volume that takes the storage hit; where user domain installation means it's the home volume that takes the storage hit. And if runtime and application are split, then backup and restore strategy has to account for this split or it's possible the application ends up "broken" if the runtime is missing.
My gut instinct is that the first user created by g-i-s should be an admin (in group wheel) by default. And when a user in group wheel is doing flatpak application installations, that by default they're installed on rootfs not in home, so that they're available for any user. I'm not super inclined to applications being stored in /home/<user>/.
A "neat" option would be a flatpak exported file that describes the system's flatpak state (all remotes, runtimes, applications) that can be imported into a clean system, and then ask flatpak to do the restore or whatever other command means "make it go" and then flatpak goes out and downloads and installs those items.
Last, I'd rather not have to manage or even be aware of runtimes. Can't the application flatpak define what runtime(s) it prefers in order, and then go out and get them? This especially applies to GNOME Software which shows runtimes separate from the application.
Chris Murphy
On Wed, 2017-02-22 at 12:37 -0700, Chris Murphy wrote:
It'd be nice if there were a direct download + install for flatpak applications. Either licking on the URL in Firefox causes GNOME Software to autolaunch and do whatever needs to be done (find and install runtimes as well as the application); or maybe an included webextension for Firefox that can do the installation.
If you go here, that is pretty much what you get: http://flatpak.org/apps.html
There's still some polish that we need to do in gnome-software to make this experience as smooth as it can be, but the basic functionality is there now.
At the moment I'm confused about --system vs --user installation locations. Somehow I have some things that are system and others are user. This is relevant because a system domain installation means it's the rootfs volume that takes the storage hit; where user domain installation means it's the home volume that takes the storage hit. And if runtime and application are split, then backup and restore strategy has to account for this split or it's possible the application ends up "broken" if the runtime is missing.
My gut instinct is that the first user created by g-i-s should be an admin (in group wheel) by default. And when a user in group wheel is doing flatpak application installations, that by default they're installed on rootfs not in home, so that they're available for any user. I'm not super inclined to applications being stored in /home/<user>/.
gnome-software has a setting: install-bundles-system-wide, which defaults to true. You will get a polkit dialog when you try to install a flatpak. I don't think there's a need for making things more complicated.
A "neat" option would be a flatpak exported file that describes the system's flatpak state (all remotes, runtimes, applications) that can be imported into a clean system, and then ask flatpak to do the restore or whatever other command means "make it go" and then flatpak goes out and downloads and installs those items.
Last, I'd rather not have to manage or even be aware of runtimes. Can't the application flatpak define what runtime(s) it prefers in order, and then go out and get them? This especially applies to GNOME Software which shows runtimes separate from the application.
That is what is done with the .flatpakref files that I've mentioned above. The file provides gnome-software with enough information to install not just the application and its remote, but also the required runtime and their remote. Again, the gnome-software support for this is still improving, but it all works with the commandline tools.
On Wed, Feb 22, 2017 at 12:58 PM, Matthias Clasen mclasen@redhat.com wrote:
gnome-software has a setting: install-bundles-system-wide, which defaults to true.
I have LibreOffice, GIMP, and Firefox-devel installed as flatpaks, and their runtimes, that's it. The size of /home/chris/.local/share/flatpak is 5.8G. That's substantially larger than conventionally installed applications. I also can't figure out how to determine their individual share of this space being used.
I think the 50G max size for root might need to be increased in the installer to account for the extra size of these applications.
On Wed, 2017-02-22 at 21:14 -0700, Chris Murphy wrote:
On Wed, Feb 22, 2017 at 12:58 PM, Matthias Clasen <mclasen@redhat.com
wrote:
gnome-software has a setting: install-bundles-system-wide, which defaults to true.
I have LibreOffice, GIMP, and Firefox-devel installed as flatpaks, and their runtimes, that's it. The size of /home/chris/.local/share/flatpak is 5.8G. That's substantially larger than conventionally installed applications. I also can't figure out how to determine their individual share of this space being used.
I think the 50G max size for root might need to be increased in the installer to account for the extra size of these applications.
flatpak list -d flatpak list --runtime -d
shows sizes
On Thu, Feb 23, 2017 at 8:28 AM, Matthias Clasen mclasen@redhat.com wrote:
On Wed, 2017-02-22 at 21:14 -0700, Chris Murphy wrote:
On Wed, Feb 22, 2017 at 12:58 PM, Matthias Clasen <mclasen@redhat.com
wrote:
gnome-software has a setting: install-bundles-system-wide, which defaults to true.
I have LibreOffice, GIMP, and Firefox-devel installed as flatpaks, and their runtimes, that's it. The size of /home/chris/.local/share/flatpak is 5.8G. That's substantially larger than conventionally installed applications. I also can't figure out how to determine their individual share of this space being used.
I think the 50G max size for root might need to be increased in the installer to account for the extra size of these applications.
flatpak list -d flatpak list --runtime -d
org.gnome.Sdk.Debug/x86_64/3.20 is 4.2GiB on its own, so that's where the bulk of this is. Anyway, I'd say Fedora 26 or for sure Fedora 27, will need an adjustment to the partitioning layout to account for these larger sizes. Easiest in the short term is to bump the max size limiter above 50G, maybe 65G is enough. Better would be to take advantage of storage pooling.
On Thu, 2017-02-23 at 09:40 -0700, Chris Murphy wrote:
org.gnome.Sdk.Debug/x86_64/3.20 is 4.2GiB on its own, so that's where the bulk of this is. Anyway, I'd say Fedora 26 or for sure Fedora 27, will need an adjustment to the partitioning layout to account for these larger sizes. Easiest in the short term is to bump the max size limiter above 50G, maybe 65G is enough. Better would be to take advantage of storage pooling.
Not sure how these ended up on your system, but the summary about debuginfo with flatpak is:
- We never install it without you asking for that explicitly - We update it automatically with the app/runtime - We remove it automaticlaly with the app/runtime
So, you should just
flatpak uninstall *.Debug
and look at the sizes again (and no, that wildcard will not work, I think you have to spell out the things you want removed).
desktop@lists.fedoraproject.org