Once again I try to get a handle of my various dotfiles and configs. This time I take another stab at gnu stow as it is often recommended. I do not understand it.

Here’s how I understand it: I’m supposed to manually move all my files into a new directory where the original are. So for ~ I make like this:

~
  - dotfiles
      - bash
         dot-bashrc
         dot-bash_profile
      - xdg
            - dot-config
                user-dirs.dirs
      - tealdeer
            - dot-config
                - tealdeer
                       config.toml

then cd ~/dotfiles && stow --dotfiles .

Then (if I very carefully created each directory tree) it will symlink those files back to where they came from like this:

~
  .bashrc
  .bash_profile
   - .config
        user-dirs.dirs
      - tealdeer
          config.toml

I don’t really understand what this application is doing because setting up the dotfiles directory is a lot more work than making symlinks afterwards. Every instructions tells me to make up this directory structure by hand but that seems to tedious with so many configs; isn’t there some kind of automation to it?

Once the symlinks are created then what?

  • Tutorials don’t really mention it but the actual manual gives me the impression this is a packager manager in some way and that’s confusing. Lots of stuff about compiling

  • I see about how to combine it with git. Tried git-oriented dotfile systems before and they just aren’t practical for me. And again I don’t see what stow contributing; git would be doing all the work there.

  • Is there anything here about sharing configs between non-identical devices? Not everything can be copy/pasted exactly. Are you supposed to be making git branches or something?

The manual is not gentle enough to learn from scratch. OTOH there are very very short tutorials which offer little information.

I feel that I’m really missing the magic that’s obvious to everyone else.

  • lelgenio
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 month ago

    That’s… all stow does, there’s nothing more to it. If you need some other feature don’t waste your time trying to make it work with stow, It’s just a meme in my opinion.

    About the “package manager” functionality, stow was originally supposed to be a development tool for the Perl programming language, you download a bunch of libraries into a directory, then use stow to merge those files into the root of your project (like a caveman), as it turned out some people started using it to manage dotfiles, and here we are.

    When I started trying to organize my dotfiles, I started with stow, but quickly found it very limited.

    After that I found dotdrop, which is considerably more involved, but gives you total control. My config with dotdrop quickly started growing insanely huge, at some point I even had system-wide systemd services declared.

    Then I found out I was basically reinventing nixos and home-manager, so I switched to that.