For example, theming shouldnt have to be a 10 step process. Make Flatpaks use your themes correctly. Another thing is QT Theming, why is it outside of KDE you can’t use the breeze style? It’s the best and most consistent application style for QT apps. And the final point, when is the naming scheme of org.foo.bar going to be fixed to be the actual name of the package rather than the technical name. Flatpak remove and flatpak install both work without giving the full name, so why doesn’t flatpak run? The naming is the only thing snaps have over flatpak. If nothing is been done how can I contribute?
The org.foo.bar thing is done so that multiple packages with the same name can coexist. It’s a design choice, not something that gets fixed. It would be nice to be able to type in the name of the package and it looks for the package like in flatpak remove and install though.
The problem with “org” part. We’ll never have org.gnome and com.gnome packages. Some apps have io.github.foo.bar. This entire thing is also case sensitive, so I have to guess is org.gnome.epiphany right name or org.gnome.Epiphany.
But you don’t have to guess package names. Installing a Flatpak adds an entry to the Applications menu so you already have a shortcut. If for some reason you need to find out the names, there’s
flatpak list.I shouldn’t have to, and my main point is flatpak remove and flatpak install both work for the sensible names (without the org/com prefix/suffix), but flatpak run does not.
alias shortname ‘flatpak run longname’
I think he means that he shouldn’t even need to do that. If it works for flatpak install it should work for flatpak run.
I just do flatpaks install something and it finds a few packages named something and let’s me chose. What else do we need, besides flatpaks being more cli friendly?
flatpak run also doing that
Like -Ss in pacman/yay. It’s so useful.
Yay is the best package manager I’ve ever used.