Re: compromise for case-challenged file systems?

[Pádraig Brady]

On 17/05/15 10:55, Pádraig Brady wrote:
> On 17/05/15 00:34, Jim Meyering wrote:
>> I noticed that since the addition of the file,
>> tests/tail-2/F-vs-rename.sh, one can no longer
>> clone coreutils onto a case-challenged file system,
>> because there is also a file in that directory whose
>> name differs only in the case of the "f":
>>
>>   tests/tail-2/f-vs-rename.sh
>>
>> What do you think about fixing this?
>> Since it's easy to avoid, you may want to write a
>> syntax-check rule using something like this:
>>
>>   $ git ls-files|tr '[:upper:]' '[:lower:]'|sort|uniq -d
>>   tests/tail-2/f-vs-rename.sh
>>
>> Actual consequence?
>> When I clone onto an hfs file system (OS/X), the initial
>> is shown as unclean, with tests/tail-2/F-vs-rename.sh
>> being shown as modified (with the differences to transform
>> it to the contents of the lower-case-named file).
> 
> Yes it's definitely worth avoiding that issue.
> Proposed patch attached.

To support a VPATH build and correct dependencies,
this is needed on top:

diff --git a/cfg.mk b/cfg.mk
index 5487d08..8799297 100644
--- a/cfg.mk
+++ b/cfg.mk
@@ -309,8 +309,8 @@ check-programs-vs-x:
        exit $$status

 # Ensure we can check out on case insensitive file systems
-sc_case_insensitive_file_names:
-       @git ls-files | sort -f | $(srcdir)/src/uniq -Di | grep . && \
+sc_case_insensitive_file_names: src/uniq
+       @git ls-files | sort -f | src/uniq -Di | grep . && \
          { echo "$(ME): the above file(s) conflict on case insensitive" \
          " file systems" 1>&2; exit 1; } || :