On 21/06/25 19:27, Werner Koch wrote:
On Wed, 18 Jun 2025 14:52, bbhtt said: Too large of a patch for a very special setting. And we have a proper solution already.
That's fine, we can carry it :)
What you can also do is to examine an environment variable and set the rspecive options depending on the envvar. For example assuming you have a INSIDE_FLATPACK set to a non-zero value: [getreg flatpack INSIDE_FLATPACK] [if $flatpack] change-std-env-name -WHATEVER change-std-env-name -OTHERTHING [fi] Either in the global or in the local conf file.
I don't think that works here. The canonical way of checking if something is running inside Flatpak is to test for the existence of the file `/.flatpak-info` inside the sandbox. But the gpg-agent is running on host, it is not running inside the sandbox. I don't think it has any idea whether the forwarded stdenvnames is coming from "GPG on host" vs. "GPG running inside the Flatpak container". - bbhtt https://bbhtt.space _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
