Wow, thanks for the reply, nice find! I did some poking around on my Linux system and even re-arranging the home folder was a task of its own because the system kept trying to replace folders in their original places. I will do some digging in to Gobo and see how they're handling this. Thanks again for pointing this out.

  > the system kept trying to replace folders in their original places.

This is the file that you want:

  $ cat ~/.config/user-dirs.dirs 
  XDG_DESKTOP_DIR="$HOME/"
  XDG_DOWNLOAD_DIR="$HOME/Downloads"
  XDG_TEMPLATES_DIR="$HOME/"
  XDG_PUBLICSHARE_DIR="$HOME/"
  XDG_DOCUMENTS_DIR="$HOME/"
  XDG_MUSIC_DIR="$HOME/"
  XDG_PICTURES_DIR="$HOME/"
  XDG_VIDEOS_DIR="$HOME/"

That helps, but be warned that there are still programs running around that just hardcode their paths

Cries in nixpkgs

(Anyone who tried to package a program that hardcodes the “usual” binary paths know the pain)

Doesn't nix itself hardcode the nix store path though?

Afaik there is an option to change it, but it is not advisable as that will break the binary cache and you are left with compiling everything yourself. This is due to a technical limitation in that different packages can contain paths everywhere and thus they are inherently part of the resulting hash, on which other packages can depend.

You’re clearly a more capable user than me, but even so, take care. The time I accidentally moved /etc has scarred me for life.

Early on in my Linux-using-life I made the mistake of deleting /etc. That was a learning experience like no other :)

Since Live CDs/Flash drives were invented, I wouldn't worry about this stuff any longer. Certainly have your personal files in a centralized location and backed up first.

Probably the easiest way to experiment these days is to create a VM and make snapshot, then start knocking down walls, just to see when and where the house collapses. Then revert and try something new.

There's a computer game that deletes random files when you make a mistake or lose.

There could be a competition!

A couple of weeks after moving to UNIX from MSDOS, I thought I'd remove lots of unnecessary 'dot-directories' from the /tmp directory. I was root as I had no concept of being a 'normal user'.

So I ran two simple commands:

     cd /tmp
     rm -fr .*

and wondered why it was taking so long. <grin>

At least that doesn't happen today anymore. From bash:

> When a pattern is used for pathname expansion, the character ``.'' at the start of a name or immediately following a slash must be matched explicitly, unless the shell option dotglob is set. The filenames ``.'' and ``..'' must always be matched explicitly, even if dotglob is set.

I did that on my NAS a few years ago. I had copied in a bunch of directories from a mac and they all had tons of dot files in each dir that were showing up on my windows machines. I popped open a terminal and did the exact same thing and wiped most of the NAS out =P Good thing I had it mirrored with my other synology.

How do you deal with lack of being able to just point to "/usr/lib/include" or other things when saying "here's my directory of shared libs"?

This is definitely interesting though, and an improvement I would say

GoboLinux symlinks everything into an FHS-ish structure under /System/Index/ so you still have a single place where binaries/libraries/includes/etc. live. (There are also symlinks from /usr/lib, /usr/bin, and others into /System/Index/ for compatibility with programs where those might be hardcoded.)

That actually seems like some low hanging fruit to go on a commit spree correcting code that hard codes paths

GoboLinux is old enough to vote in most countries.

So either those low hanging fruits are higher than they seem, or we're all just a bunch of dwarves.

My bet is on the second option.

It is low hanging fruit as far as the software is concerned. Simply parameterize all paths.

Will upstream accept such patches though? Sounds unlikely to me.

Dammit, I wanted to be the one to mention gobo linux [HN deleted my laughing emoji ffs]

Beat the system ʕ•ᴥ•ʔ