Having to prefix commands with “flatpak run org.whoever.whatever…” gets old quickly, and setting aliases to get around it isn’t user friendly. It’s certainly possible, it’s just not practical (which may have been a better word to use than “feasable” in my first comment).
They can potentially work on that, in the same way they do desktop files to make gui integrate better there could be some sort of mechanism for cli to integrate better.
Let’s paraphrase to “CLI applications are quite cumbersome to use under Flatpak as per the current implementation”.
Unless you set up your own aliases, you’ll have to write out commands like flatpak run ..., and if you don’t know the package name yet you’ll need to run flatpak list --app first as well
I hope that in the future, Flatpak gets some improvements for exporting CLI utilities into the user’s environment.
Simply wrong, there are already lots of CLI applications on flatpak.
Having to prefix commands with “flatpak run org.whoever.whatever…” gets old quickly, and setting aliases to get around it isn’t user friendly. It’s certainly possible, it’s just not practical (which may have been a better word to use than “feasable” in my first comment).
They can potentially work on that, in the same way they do desktop files to make gui integrate better there could be some sort of mechanism for cli to integrate better.
Let’s paraphrase to “CLI applications are quite cumbersome to use under Flatpak as per the current implementation”.
Unless you set up your own aliases, you’ll have to write out commands like
flatpak run ..., and if you don’t know the package name yet you’ll need to runflatpak list --appfirst as wellI hope that in the future, Flatpak gets some improvements for exporting CLI utilities into the user’s environment.