For me it’s kinda a problem that we don’t have only ONE unified UI for softwares. Problem one side Gnome Softwares handles flatpacks, and rpms, what is great. But nightmare turns on, gets confusing when I or someone has installed something in flatpacks, and want to remove with standard dnf remove. Currently dnf doesn’t track installed flatpacks, therefore the simple response as no such installed software in cli is could bad, if the user search something - but need to use multiple paths to manage softwares IMHO.
Kinda messy when I hit dnf update or dnf upgrade what runs down, then Gnome software still wants to separately update and upgrade AND restart. Basically I don’t get it why dnf and Gnome softwares don’t know about each others jobs or makes it possible to do both ways, or do at least ALL tasks one unified way.
Gnome Softwares shows the source at the installer, but when switch to installed packages, there is no info about the source or group selection…
So, any advice, or alternative that actually replaces and makes it manageable the softwares, and maybe it sees other sources?
The mess exists because this are different systems where came up on different epochs/times. The software app is made exclusive for the Gnome desktop. Software is able to check Flatpak, the usual Gnome apps inclusive the Extensions. It also checks the usual Fedora packages like dnf does.
The dnf app is a package manager for RPM-based Linux distributions. It resolves the dependencies. With this app we do install on the command-line for those version who not use Desktop environments or if we want to control/install within a script on the terminal.
Everithing what is gnome-shell specific uses this prefix.
For example if you look for an extension you can find it like sudo dnf list gome-shell-extension*
Dash to dock you would find this way sudo dnf list gnome-shell-extension-d*
This means flatpak has a own command line tool you have to check if you want to manage the flatpacks within a script or in the terminal. Just check man flatpak