On Tue, 24 Dec 2019, 23:52 Neil Horman, <nhorman(a)redhat.com> wrote:
On Tue, Dec 24, 2019 at 05:02:54PM
So, is it flatpak thats creating these sockets then? If thats the case,
maybe
adjust flatpak to store sockets in /tmp/<nonce>/<id>, and symlink to them
from
$HOME/var/.App/appid?
Alternatively, just store text files in $HOME/var/.app/appid, and store the
socket descriptor that you want to use in said text file
Neil
Merry Christmas to everyone!
Not flatpak creates them the application provided as flatpak does. What
flatpak should do is properly workaround this instead of relying on
accident that an application works. I have a workaround changing the
default flatpak directory but flatpak devs should find a proper way to do
this...
On Wed, 25 Dec 2019, 12:45 Damian Ivanov, <damianatorrpm(a)gmail.com> wrote:
On Tue, 24 Dec 2019, 23:52 Neil Horman, <nhorman(a)redhat.com> wrote:
> On Tue, Dec 24, 2019 at 05:02:54PM
> So, is it flatpak thats creating these sockets then? If thats the case,
> maybe
> adjust flatpak to store sockets in /tmp/<nonce>/<id>, and symlink to
them
> from
> $HOME/var/.App/appid?
>
> Alternatively, just store text files in $HOME/var/.app/appid, and store
> the
> socket descriptor that you want to use in said text file
>
> Neil
Not flatpak creates them the application provided as flatpak does. What
flatpak should do is properly workaround this instead of relying on
accident that an application works.