Closed PaulMansour closed 4 years ago
I vaguely remember scenarios like this were an argument for case coding all the time, regardless how ugly it looks.
Without considering all of the consequences I've implemented this by reporting and refusing to write any of the duplicate folders or items. But only in case-agnostic OSs. (windows &c.) with casecode Off.
No problem is sought, reported or averted if CreateProject
is being run in a case-sensitive OS determined by the absence of either of /project/aplsource/ and /project/APLSOURCE/ after /project/APLSource/ has been created.
It might be better if the checks were done willy-nilly, the potential problem reported in either case but only averted for case-agnostic OSs with casecode Off as at present.
The reporting in the case-sensitive OS would warn of the problem were the project to be copied or cloned (is that the right word?) into a case-agnostic OS, naming the offending folders and items.
I suspect acre would be incapable of recognising the problem after the fact as the folders would already have been merged and the files overwritten before acre got hold of them.
Acre does not warn that same-name-different-case folder names exists when creating with casecode=off, and misbehaves by merging the contents!