Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS-specific configurations #286

Open
tim-coutinho opened this issue Dec 17, 2020 · 2 comments
Open

OS-specific configurations #286

tim-coutinho opened this issue Dec 17, 2020 · 2 comments

Comments

@tim-coutinho
Copy link
Contributor

Is this something that's up for consideration? I use different operating systems for work vs. my personal computer. As of now, I'm controlling which files are backed up and/or reinstalled with something like [[ $OSTYPE =~ 'linux' ]] or [[ $OSTYPE =~ 'darwin' ]] in the condition fields, but it doesn't make much sense to backup shallow-backup.conf itself due to paths differing based on the OS, e.g. on my Macbook, my Sublime Text settings are at /Users/$USER/Library/Application Support/Sublime Text 3/Installed Packages, while on my personal Windows machine with WSL, they're at /mnt/c/Users/$USER/AppData/Roaming/Sublime Text 3. The backup_path potentially differs for both as well.

Basically, more programmatic parsing of shallow-backup.conf is what I'm looking for.

@alichtman
Copy link
Owner

alichtman commented Dec 17, 2020

I'm open to re-engineering this feature. It was a duct-tape patch originally to get minimal functionality for me to use it across my devices, but definitely has some shortcomings (like you mentioned).

It would be a good idea to fix this.

One idea is separate top level keys per-OS. This leads to a lot of duplication, so maybe we could have a default backup profile and then OS-specific overrides.

@tim-coutinho
Copy link
Contributor Author

Sounds good, I'll potentially look into giving it a shot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants