But while we’re on the subject, ~/.local/share is cancer and shouldn’t exist.
The appropriate path is /usr/share.
I have a SystemD service that will erase anything written to that godforsaken .local folder, and if that breaks your shitty software then I’ll assume your shitty software doesn’t work and delete it and spam issues about it until you fix it or find a different career doing something productive, like cooking McRibs.
I’m a little confused by that statement. Where should locally installed (non-sudo) applications, such as virtual python envs who are accessed by multiple other not-necessarily-python apps or perhaps baloo, flatpak, etc, store their shared data? I’m rather convinced that giving all users write access to /usr/share is a terrible idea.
He’s using windows.
But while we’re on the subject, ~/.local/share is cancer and shouldn’t exist.
The appropriate path is /usr/share.
I have a SystemD service that will erase anything written to that godforsaken .local folder, and if that breaks your shitty software then I’ll assume your shitty software doesn’t work and delete it and spam issues about it until you fix it or find a different career doing something productive, like cooking McRibs.
That’s a global folder, and not proper for storing “per user” data.
/usr/share? How is a random app getting write permissions to that?
I’m a little confused by that statement. Where should locally installed (non-sudo) applications, such as virtual python envs who are accessed by multiple other not-necessarily-python apps or perhaps baloo, flatpak, etc, store their shared data? I’m rather convinced that giving all users write access to /usr/share is a terrible idea.
The irony is how lennart and his cancer approached standards, top to bottom.
Now I want McRibs.