-
-
Notifications
You must be signed in to change notification settings - Fork 390
Support for avoiding overwrite upon opening archive #22
Comments
Are you sure? I thought we already don't overwrite existing files when extracting... |
Not sure, but here is the behavior I'm getting. I have two files, and I archive only one of them. After archiving and then opening the archive in the same folder, the modified timestamp of the extracted file that came from the archive changes (from
The problem this creates, for me, is that when I re-archive the exact same file it creates a "different" archive because of the modified timestamp, and I'm using the md5 hashes to test differences in local/remote archives.
|
Hmm, maybe we are now. I don't think that is intended. Want to submit a PR? :) Basically, return an error if a file already exists when extracting. Should just be a few lines. (Test welcome too if you're able!) I'm just super busy with stuff right now. |
Sure! I'd be happy to! |
@schollz would you be interested in submitting the PR? checking again as its been a while |
Is this change live? when I try to unarchive a file, it still overrides an existing one |
Not yet! Would you be willing to test your scenario using PR branch? #89 |
This feature is under way in #99 |
Hi @mholt, this is a great tool/library!
I've found it useful to avoid overwriting files if they already exist when opening an archive to a folder. I'm wondering if you'd like to incorporate this as an option to your library? Here's my change: schollz@8b912ca. Of course, it would need to be amended so it can be toggled as optional.
The text was updated successfully, but these errors were encountered: