The appropriate path is /usr/share.
That’s a global folder, and not proper for storing “per user” data.
Comment on Developers: "Yes, the users love cluttered homes, just put everything there and ignore guidelines"
LainTrain@lemmy.dbzer0.com 2 weeks agoHe’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 Cron job that will erase anything written to that folder, and if that breaks your shitty software then I’ll assume your shitty software doesn’t work and I’ll also spam issues about it until you fix it or find a different career doing something productive, like cooking McRibs.
Buffalox@lemmy.world 2 weeks ago
ekky@sopuli.xyz 2 weeks ago
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.
corsicanguppy@lemmy.ca 2 weeks ago
I have a SystemD service
The irony is how lennart and his cancer approached standards, top to bottom.
Now I want McRibs.
dev_null@lemmy.ml 2 weeks ago
/usr/share? How is a random app getting write permissions to that?