5 ms·

>But polluting your home directory like ~/go, without even the decency to hide it, is extremely rude and offensive. Counterpoint: I actually like having visib

by sevagh 2y ago

>But polluting your home directory like ~/go, without even the decency to hide it, is extremely rude and offensive. Counterpoint: I actually like having visible directories, versus having to figure out where in /usr/share or /usr/local/ or ~/.local or /var an installer chose to sneak their files in. I got used to it and in HOME I put some of my manually installed tools like `AMD_AOCL` for the AMD AOCL libraries, `Android/android-studio` for Android Studio, `intel` for IPP/OpenAPI, etc. Don't want it anymore? Easy rm -rf, no need to go digging for where it could be hidden.

KTibow 2y ago
In theory, all applications following XDG would also solve the problem, as it has only 1 configuration directory. (Although I admit some apps use the data directory which brings it up to 2)
- SAI_Peregrinus 2y ago
  XDG isn't enforced, it's voluntary. So there will always be lots of applications not following it.
AlecSchueler 2y ago
The point of XDG is to take the guesswork out of it by having applications follow your stated preferences.
megadog3 2y ago
"I actually like having visible directories, versus having to figure out where in /usr/share or /usr/local/ or ~/.local or /var an installer chose to sneak their files in." You seem to be mixing together two concepts here: 1. The files created by the installer, which are handled by the package manager. I can consult my package manager for files created by a specific package: pacman -Ql package_name. 2. The files created after installation (user preferences, plugins). The program should follow the XDG specification.
- sevagh 2y ago
  I don't worry about where my distro package manager installs files. Some install methods are outside of your package manager, but try to touch /usr or /opt or /var, like NVIDIA sh scripts and the likes.
  - bmicraft 2y ago
    And those should be avoided as much as possible because they're always problematic and break randomly. How could they not break, when the package manager doesn't even know they exist or what they depend on?
    - sevagh 2y ago
      Well now we're going around in circles: 1. External install scripts that put stuff in system directories are sloppy and we don't like them 2. External install scripts that put stuff clearly-named non-hidden directory in your $HOME are better than the above

by sevagh 2y ago

KTibow 2y ago

In theory, all applications following XDG would also solve the problem, as it has only 1 configuration directory. (Although I admit some apps use the data directory which brings it up to 2)

SAI_Peregrinus 2y ago
XDG isn't enforced, it's voluntary. So there will always be lots of applications not following it.

AlecSchueler 2y ago

The point of XDG is to take the guesswork out of it by having applications follow your stated preferences.

megadog3 2y ago

"I actually like having visible directories, versus having to figure out where in /usr/share or /usr/local/ or ~/.local or /var an installer chose to sneak their files in." You seem to be mixing together two concepts here: 1. The files created by the installer, which are handled by the package manager. I can consult my package manager for files created by a specific package: pacman -Ql package_name. 2. The files created after installation (user preferences, plugins). The program should follow the XDG specification.

sevagh 2y ago
I don't worry about where my distro package manager installs files. Some install methods are outside of your package manager, but try to touch /usr or /opt or /var, like NVIDIA sh scripts and the likes.
- bmicraft 2y ago
  And those should be avoided as much as possible because they're always problematic and break randomly. How could they not break, when the package manager doesn't even know they exist or what they depend on?
  - sevagh 2y ago
    Well now we're going around in circles: 1. External install scripts that put stuff in system directories are sloppy and we don't like them 2. External install scripts that put stuff clearly-named non-hidden directory in your $HOME are better than the above