It’s about making sure you know what is inside the flatpaks. If you make your own set of flatpaks, you can distribute them with the OS. It’s not that fedora flatpaks aren’t distro-agnostic, you can use them on any distro. They just want a set where they can verify the build process and trust.
I think, because of Fedoras atomic desktops. I didn’t use any of them yet, but it seems like Flatpaks should be used there, since one should (or can?) not install tradional packages there. Therefore Fedora provides the flatpaks anyway and they can be used on the non atomic desktops as well.
Another reason is, that you might not be able to install the latest version of an application as rpm package if a required dependency in the repo is outdated. A Flatpak usually does not have the issue since a newer version would include the fitting runtime.
This said, I do think its not this big of an issue for fedora which is usually quite up to date. But if you run a distribution with LTS releases or something like Debian you will much more likely have older dependencies in your repositiry.
i guess it makes sense in that case, but i’m really not convinced flatpaks should be used as the default (or only, apparently) way to install every application in the system. flatpak’s flexibility is great for the particular cases where you want to install newer versions of applications or if an application isn’t available in the official repos somehow. besides that, just use distro packages
Another reason is, that you might not be able to install the latest version of an application as rpm package if a required dependency in the repo is outdated
Indeed. I believe most users will just switch to flathub. Sort of how most users will install some codecs, but it can’t legally be included in the base install.
It’s about making sure you know what is inside the flatpaks. If you make your own set of flatpaks, you can distribute them with the OS. It’s not that fedora flatpaks aren’t distro-agnostic, you can use them on any distro. They just want a set where they can verify the build process and trust.
then why not just use regular packages?
I think, because of Fedoras atomic desktops. I didn’t use any of them yet, but it seems like Flatpaks should be used there, since one should (or can?) not install tradional packages there. Therefore Fedora provides the flatpaks anyway and they can be used on the non atomic desktops as well.
Another reason is, that you might not be able to install the latest version of an application as rpm package if a required dependency in the repo is outdated. A Flatpak usually does not have the issue since a newer version would include the fitting runtime. This said, I do think its not this big of an issue for fedora which is usually quite up to date. But if you run a distribution with LTS releases or something like Debian you will much more likely have older dependencies in your repositiry.
i guess it makes sense in that case, but i’m really not convinced flatpaks should be used as the default (or only, apparently) way to install every application in the system. flatpak’s flexibility is great for the particular cases where you want to install newer versions of applications or if an application isn’t available in the official repos somehow. besides that, just use distro packages
doesn’t flathub solve that already?
Indeed. I believe most users will just switch to flathub. Sort of how most users will install some codecs, but it can’t legally be included in the base install.