Comment by Andrew Benson (JIRA)

Just trying to clarify here...

@aciidb0mb3r – you are saying the issue is with varying case for case-sensitive filesystems may have a target folder name that's different from the casing in the Package.swift – is that correct?

In the case of /some/path/to/project/TargetName, you would want to use "TargetName" even if the manifest shows "targetname"?

What about TARgetNAme? Or if there are several matching entries, such as targetname, TargetName, TARGETNAME, and targetNAME?

What would be the proper behavior in this case?

Are you sure matching the name case insensitively for case-sensitive filesystems is really the right behavior at all?

Ideally, we should have never allowed this but existing packages will break if we change the behavior now. We could, however, start emitting a warning in these cases but still accept the right path on disk. I don't think you can have multiple directories with the same name but different casing on a case-insensitive file system.

Comment by Andrew Benson (JIRA)

On a case IN-sensitive filesystem, you are right, that you cannot have multiple directories with different cases. However, for case-SENSITIVE filesystems, you can definitely have that – directories named "Hello", "hello", and "heLLo" can all coexist, for example.

Right, this is only a problem for case-insensitive file systems. For case-sensitive filesystem, we'll use whatever is in the manifest and fail if it doesn't exactly match (this should already be the case).

Comment by Andrew Benson (JIRA)

Okay, so what problem is this trying to solve?

In a case-insensitive filesystem if we try to access “foo” but instead get “Foo”, doesn’t that already work as expected?

Or is the issue that we explicitly check if “foo” exists at some point, rather than just trying to access it, and this are told NO, since the filename on disk is “Foo”?

> Or is the issue that we explicitly check if “foo” exists at some point, rather than just trying to access it, and this are told NO, since the filename on disk is “Foo”?

Right. Some tools like the indexer rely on getting the right casing. I am now wondering if it's even possible to do something about this without knowing if the filesystem is case-insensitive or not. I'll need to think more about possible solutions here.

master: #2216

5.1: #2217

This is completed, correct?

@tomerd looks like this was already implemented per this comment: #4699 (comment)