I’m new. I only just took my first few steps into the world of Linux like 2-3 weeks ago to set up a Pi-hole VPN. From what I can gather in other comments is that flatpak is a program that optimizes storage by keeping any program and it’s dependent files in one place instead of having dependencies spread out amongst system folders. The drawback would be that running simple commands like OP did don’t work because the files are either held in an unexpected place according to the repository or they files were technically installed in their respective folders, then moved to their respective container by flatpak which marks them as having been “used”. The other drawback seems to be system overhead. The container system must use a bunch of storage.
That’s what I took from the post and comments anyway.
It doesn’t optimise storage, it does exactly the opposite. The point is to try to reduce dependencies by having everything in one atomic unit. This means if two programmes would use the same library you waste space by having it installed twice, but if two programmes use different versions of the same library you don’t have dependency problems because they each have their own copy to work from. I can see the pros and cons but personally I don’t have a use for it so I avoids it
I’m new. I only just took my first few steps into the world of Linux like 2-3 weeks ago to set up a Pi-hole VPN. From what I can gather in other comments is that flatpak is a program that optimizes storage by keeping any program and it’s dependent files in one place instead of having dependencies spread out amongst system folders. The drawback would be that running simple commands like OP did don’t work because the files are either held in an unexpected place according to the repository or they files were technically installed in their respective folders, then moved to their respective container by flatpak which marks them as having been “used”. The other drawback seems to be system overhead. The container system must use a bunch of storage.
That’s what I took from the post and comments anyway.
It doesn’t optimise storage, it does exactly the opposite. The point is to try to reduce dependencies by having everything in one atomic unit. This means if two programmes would use the same library you waste space by having it installed twice, but if two programmes use different versions of the same library you don’t have dependency problems because they each have their own copy to work from. I can see the pros and cons but personally I don’t have a use for it so I avoids it