search

flathub-infra / flatpak-builder-lint

A linter for flatpak-builder manifests
MIT License
50 stars 126 forks source link

Add io.gitlab.liferooter.TextPieces to exceptions #387

Closed liferooter closed 5 months ago

liferooter commented 5 months ago

I'm the developer of Text Pieces. I've just finished rewritting it. During the rewrite, it was moved from GitHub to GitLab with corresponding ID change. So now it's not com.github.liferooter.textpieces, but io.gitlab.liferooter.TextPieces. So I need to add it to the list of exceptions, because it still needs --talk-name=org.freedesktop.Flatpak permission.

bbhtt commented 5 months ago

Do you have some docs/examples around what kind of commands it needs to run?

liferooter commented 5 months ago

It needs to run user-defined commands.

The application is a developer scratchpad with ability of performing some text actions, like hash calculation, JSON formatting and much more. For all of this actions there are no need for sandbox escape of course. But it also allows to define your own actions in any script language you prefer. The application just gives the user an executable text file and they can write in it any script they want in any language they prefer (as long as it can run files via shebang) and then use it as a custom action. The application uses flatpak-spawn --host to run these scripts outside the sandbox. It's required to allow the user use anything from their host system environment, e.g. some libraries and languages they prefer or even some data from the host system (e.g. someone could want to use custom script for GPG encryption and signing, so they would need to access gpg-agent and ~/.gnupg). This allows the sandbox to be transparent for the application users and do not interfere with the application usage.