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

Way to mark files to not be overwritten when updating #48

Open
cfillion opened this issue May 24, 2022 · 0 comments
Open

Way to mark files to not be overwritten when updating #48

cfillion opened this issue May 24, 2022 · 0 comments

Comments

@cfillion
Copy link
Owner

Would be useful for shipping configuration files as their final filename and not overwriting them at each update. Could be combined with the checksum feature to detect whether they have been modified by the user and prompt whether to overwrite? (Or save with a .new suffix like pacman does?)

@cfillion cfillion changed the title Way to mark files to not be overwriten when updating Way to mark files to not be overwritten when updating May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant