About the image: The joke’s on you, I install my flatpaks via the terminal.
I’ve started using flatpaks more after starting using Bazzite and I liked them more than I expected. As a dev, I still need my work tools to be native, but most of my other needs are well covered by flatpaks.
Tip: Flatseal is a great config manager for flatpaks’ permissions.
I replaced Firefox system package with Flatpak because I think browser is the most used and vulnerable thing in my system. And the size seemed reasonable.
I did not replace Thunderbird because its size is almost 10 times.
Installing them is not difficult. It’s the same as any other flatpak.
The problem is when running them (actually, when running any flatpak, not just CLI tools) you need to type out the whole backwards domain thingy that flatpaks use as identifier, instead of having a proper typical and simple executable name like they would have if they were installed normally.
I end up adding either symlinks or aliases for all my flatpaks because of this reason. After doing that it’s ok… but it’s just an extra step that’s annoying and that the flatpak devs have no interest on fixing apparently.
About the image: The joke’s on you, I install my flatpaks via the terminal.
I’ve started using flatpaks more after starting using Bazzite and I liked them more than I expected. As a dev, I still need my work tools to be native, but most of my other needs are well covered by flatpaks.
Tip: Flatseal is a great config manager for flatpaks’ permissions.
Installing flatpaks via the terminal is so much faster for some reason, so I always do it that way.
I installed flatseal but I never understand what is essential and what is not.
It is mostly trial and error. I use it mostly to set envvars.
As an example, I add the ~/.themes folder and the GTK_THEME to allow some apps to get the themes I downloaded.
Oh, so flatpaks cannot automatically get system themes?
If it is trial and error, is it really useful for a normal user?
System themes, probably most of them work. But most of them don’t bother watching the user themes or icons folder.
I don’t think Flatseal is that useful for the majority of users, no. But it is a good tool to have in mind when the need arises.
Why do you think it is not useful?
I replaced Firefox system package with Flatpak because I think browser is the most used and vulnerable thing in my system. And the size seemed reasonable.
I did not replace Thunderbird because its size is almost 10 times.
The person you’re replying to is talking about the permissions manager flatseal, not flatpaks
Oops. I got confused
My guess was the point is that it’s difficult to install CLI tools using Flatpak
Installing them is not difficult. It’s the same as any other flatpak.
The problem is when running them (actually, when running any flatpak, not just CLI tools) you need to type out the whole backwards domain thingy that flatpaks use as identifier, instead of having a proper typical and simple executable name like they would have if they were installed normally.
I end up adding either symlinks or aliases for all my flatpaks because of this reason. After doing that it’s ok… but it’s just an extra step that’s annoying and that the flatpak devs have no interest on fixing apparently.