Email or username:

Password:

Forgot your password?
Dr. Quadragon ❌

Note to self:

Flatpak stores all of its user configuration and otherwise application-specific files in ~/.var

Which is actually great for a) not polluting ~/ and b) having all of the config in one place, finally.

Although the naming could have been a little more obvious.

3 comments
[DATA EXPUNGED]
AkhIL

@strizhechenko
Flatpak places everythong related to a single app into ~/.var/app/<app_id>
So moving/removing all app data is simple as moving/removing single directory.
@drq

[DATA EXPUNGED]
AkhIL

@strizhechenko AFAIK `local` means the same as non-local but custom and overrides non-local, like `/usr/local/bin` and `~/.local/bin` overrides `/usr/bin`, `var` means "variable" and is meant to be used as a place to store application/service volatile data. So `~/.var/flatpak/...` is more UNIX-like.

iliazeus

@akhil the convention in question is the XDG Base Directory spec:

specifications.freedesktop.org

It does not specify `~/.var`; instead, as I understood, `$XDG_DATA_HOME/flatpak` should be used; and if `$XDG_DATA_HOME` is not set, `~/.local/share` should be taken as its value.

Sadly, almost nobody does that properly anyway. Even when people try to do it the right way, they most often just hard-code `~/.local/share/whatever`, without taking that env var into account.

@strizhechenko @clacke @drq

@akhil the convention in question is the XDG Base Directory spec:

specifications.freedesktop.org

It does not specify `~/.var`; instead, as I understood, `$XDG_DATA_HOME/flatpak` should be used; and if `$XDG_DATA_HOME` is not set, `~/.local/share` should be taken as its value.

Go Up