Problem is, this still makes sense in some cases but doesn't in others, and stow, as it is, doesn't care about the distinction. For example, on a machine where

Problem is, this still makes sense in some cases but doesn't in others, and stow, as it is, doesn't care about the distinction. For example, on a machine where ~/.config/autostart/ doesn't still exist, I do not want that either ~/.config or ~/.config/autostart are created as symlinks to my stowed package; otherwise any newly installed file, from unrelated apps, would end up in my package! I just want this path to exist as a proper dir, and only contain whatever symlinks are needed from stow. Thus an `mkdir -p` is still needed before running stow. On the other hand, I do want that ~/.config/wireshark/ is a symlink to the stow repository. So no mkdir in this case. Regardless, having a script that adds extra per-package pre-process/post-process logic before/after running stow is still needed, anyway.