3 ms·
I put them in a dotfiles directory and use `stow`[1] to symlink the contents to where applications expect them to be. Under that root I have a home folder that
by marcyb5st 1y ago
I put them in a dotfiles directory and use `stow`[1] to symlink the contents to where applications expect them to be. Under that root I have a home folder that it is symlinked to `~/`, and I have and applications one that is symlinked to `Applications Support` through the `-T` argument of stow.
To this day I still have to find anything that has problems taking a symlink instead of a file.
I am pretty happy with this setup as it means that all my dotfiles are in a single root folder that I manage through a git repo.
So I don't see what the linked articled means when it says that stows "makes (unsurprisingly) no effort to support ~/Library/Application Support.". It is literally a bit of organization from your side and passing a flag.
[1] https://www.gnu.org/software/stow/ https://www.gnu.org/software/stow/
- thehours 1y agoI also use stow on MacOS and have been pretty happy with it. > […]although macOS will regularly replace your symlinks with copies of the destination files I’m curious about this claim from the article - to what extent is this true?
- marcyb5st 1y agoPersonally I never experienced it (to the best of my knowledge). Weird.
- portaltonowhere 1y agoI have never seen this behavior on macOS and doesn’t make sense. However, some applications will save files by creating a copy and overwriting. Maybe that’s what the author experienced?
- jsmeaton 1y agohttps://github.com/lra/mackup?tab=readme-ov-file#warning https://github.com/lra/mackup?tab=readme-ov-file#warning Perhaps referencing this behaviour where preference files can no longer be symlinks? > Mackup does not work correctly in macOS Sonoma and all later versions, since it does not support symlinked files for preferences.