Do dotfile fallback to allow overriding default group dotfiles for certain platforms

[cmseeling]

Hey, I recently found this utility and I really like it.

I was wondering if it would be possible to somehow merge configuration files to help cut down on duplicating files and manually syncing them.

For example, in my .gitconfig file I use the git-credential-libsecret store to save my passkey on Linux, but I don't need that on my Mac because it's stored in the Apple Keychain.

So what I would like to see is something like this file structure:

dotfiles
|--Configs
   |--git
   |  |--.gitconfig
   |--git_linux
   |  |--.gitconfig
   |--git_macos
      |--.gitconfig

In Configs/git/.gitconfig I would have something like

[user]
name = username
email = email
...
# tuckr_credential

Configs/git_macos/.gitignore would be empty since I don't need that configuration option on Mac. In Configs/git_linux/.gitconfig I would have:

[credential]
helper = 'path/to/git-credential-libsecret'

Thanks!

[RaphGL]

Hello, this is already an implemented feature. It's documented here but I forgot to write about it on the wiki page.

What is not implemented yet is doing a fallback, so if you have the same file on git and git_linux it will just symlink one of them and mark the others as conflict. I think doing the fallback thing makes sense tbh. I haven't thought of this use case before. I think it's worth investing and attempting to implement.

[cmseeling]

Thanks for replying. I did look at the conditional deployment and I'm using it for some things. The fallback is exactly what I'm looking for so I can maintain one file for the majority of the configuration that is shared between machines and then have a few very small other files for OS specific values.

[RaphGL]

I see, makes sense. Only this last year people have started to use my tool, even though I've been using it myself for 3 years. So there's these small holes in how tuckr behaves and how people expect it to behave, since I was only working on whatever affected my own use cases.

I'll definitely take a look at how I can add this. I think adding this and coupling it with this suggestion can massively reduce the amount of setup and files u have to keep track of.

[RaphGL]

This is for my own viewing mostly, these are the tasks impeding the closure of this issue:

• Make tuckr decide which groups has higher priority and symlink it
• Make individual group tracking work with fallbacks
• Make global status tracking work with fallbacks
• Consider if these 2 tracking approaches can be unified to reduce maintenance costs and potential differences

[RaphGL]

I've just fixed this issue. It took me way longer than I expected it would take me to figure out the "best" way to do this.
I've only added fallback to Configs, so it's not supported on Hooks or Secrets, I'm not sure if that's even a desirable behavior. If it is, someone please let me know so I can move the code in that direction in the future.

Also if you notice any bugs regarding this addition, please let me know. Thanks!