-
Notifications
You must be signed in to change notification settings - Fork 18
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
Colliding case-sensitive file paths on a case-insensitive filesystem #36
Comments
This came up previously: #7 How do you suggest we address this? |
I cannot see here why the capital versions are needed at all, probably using only the lowercase versions can be a fool-proof solution (but, I guess it is intentional for some reason the doubled files) |
|
I see, thanks for the explanation. |
The problem we have currently is that if the dist release tar.gz is created on a case-sensitive filesystem, but the package is being built on a case-insensitive one later (like the default macOS) then at the unpacking only one of the files remains (usually the capital one). This can lead to the issue described in #7. What I suggest is to use different file names and explicitly move/rename/delete as needed during the make phase depending on the filesystem case sensitivity. |
Case-insensitive filesystems are not currently supported (neither for |
git clone https://github.com/buytenh/ivykis.git .
Cloning into '.'...
remote: Enumerating objects: 5440, done.
remote: Counting objects: 100% (161/161), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 5440 (delta 98), reused 153 (delta 92), pack-reused 5279
Receiving objects: 100% (5440/5440), 3.04 MiB | 452.00 KiB/s, done.
Resolving deltas: 100% (3468/3468), done.
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'man3/IV_FD_PUMP_INIT.3'
'man3/iv_fd_pump_init.3'
The text was updated successfully, but these errors were encountered: