An initial release of Flatpak portals for GNOME

In a conventional distro this may happen if someone gives you a PDF and you had never seen one before. But every application producing PDFs would likely suggest a PDF viewer at install time, so you can install both together and avoid the need to have your users searching for a suitable program at inconvenient times.

In fact, my question was triggered by the instructions I found on the net for installing nextcloud as a snap in ubuntu (https://www.linux.com/learn/how-install-nextcloud-server-...) which made me a bit worried about the management of strict dependencies and suggested companion packages in a flatpack and snap world. For instance, you install the nextcloud snap, but this gives you nothing useful yet. Because you need to realize and satisfy all the dependencies yourself. You need a web server (and most likely not just a web server, but Apache and in a specific version range, if you want everything to work without tweaks), then you need a DB (in fact mysql), and a specific version of PHP. But still you do not have anything functional. You need to collect some error logs or read some deployment instructions to realize that PHP misses some packages and, one by one, see that they are zip, dom, xml writer and reader, gd, curl, mdstring. Seems fairly more complex on the admin than what traditional packaging with automatic management of dependencies would be. Obviously this could be solved by having the nextcloud "package" contain a full AMP stack and all the needed php packages, but this has other inconveniences. It is true that things have always worked in this way on OSs with no package management, but I was wondering if some better solution was in the work for flatpack or snap.