-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Prevent file name collision #1201
Comments
Can you tell me more about your specific use case? It generally does not make sense to have two DATs write their files to the same directory. That's why the various |
I was importing ps3 bios in my bios folder, igir said it has found and write 3 bioses. But when I ask a report on the bios folder it had only 1 bios. Take me some time to understand where was the problem.
If Igir had warn me it was rewriting 3 times the same filename I'll have understood faster. Maybe you're right about having two DATs write their files to the same directory, I dun know ! Ty, |
Every time I think I know what the standards of various DAT groups are, they surprise me 🙂. I'll think about how I want to handle a conflict warning/error, I think it's a good suggestion. In the meantime, I'll fix up parent/clone inference for this so you can use |
Thanks ! |
Is your feature request related to a problem?
Do not write the same file twice in one copy/move/zip/whatever.
Two use case :
Describe the solution you'd like
Igir could write a warning when it detect that it gonna overwrite a file he wrote in the same run, and of course don't overwrite.
"The name file "maria.rom" seems to be used by two games [put here games details for identification]. Currently the file "maria.rom" contains the game [the game detail]."
Additional context
No response
The text was updated successfully, but these errors were encountered: