If you have ever criticized GNOME or Flatpak in public, you will be discriminated. If you are a GNOME member, you can do anything, break all the rules. The only thing that matters is who creates the application and who is the maintainer of the package. It doesn't matter if the software is full-value or half-working (generally speaking, almost every IDE on Flathub is broken, including Visual Studio Code, Code::Blocks, JetBrains IDEs, etc.), polished or bugged, stable or unstable, safe or with security holes (we already have packages that have literally over 100 known security vulnerabilities (already marked with CVE) and no one has done anything about it for years). They are not there to provide exemplary quality, but to discriminate one software against another. I will tell you one thing: these rules are bullshit. For example, Gimpsle was accepted with the -filesystem=host access, although yet in 2018 they said that even GIMP should have lower permissions. Moreover, new submissions are still accepted with highest privileges. Moreover, for already existing packages, " patches are welcomed". The answer was as follows: " rules are fluid and just because something has been accepted before doesn't mean it would be now". I tried to confront Flathub members why new applications cannot have such permissions. It is true that most popular software on Flathub have the highest possible access to the filesystem. I know that at least some of you are familiar with the flatkill website. As you can see, my standalone package has full permissions, but I was forbidden to give the same permissions on Flathub. They always want to limit application permissions as much as possible, at least officially.Īnyway, I got at least several dozen requests (both on GitHub and IRC channel) to remove the -filesystem=host permissions from my packages. Unfortunately, Flathub members have a different opinion on this matter. I always try to give the -filesystem=host permissions, because users expect it. Well, according to the Flathub members, it's not a bug, it's a feature. Version won't allow use of secondary drives
0 Comments
Leave a Reply. |