dos filename portability in pathchk

[Eric Blake]

Wishlist items (I know - it probably won't get implemented if I don't assign
copyright and submit the patch myself...)

It would be nice if pathchk supported -d (--dos) that warned about filenames
that are not portable to Windows based systems, such as cygwin.  I don't know
whether --portability should imply -d or not.  For example,

$ pathchk --port aux.sh foo. ; echo $?
0
$ pathchk -d aux.sh foo. ; echo $?
pathchk: stem `aux' in filename `aux.sh' is nonportable to DOS
pathchk: trailing `.' in filename `foo.' is nonportable to DOS
1


And a possibility for one other option is case-sensitivity, -c.  It could warn
between conflicts of multiple arguments, or between the spelling given to
pathchk vs. the spelling on disk.  This is useful for FAT, NTFS, HFS+, and other
case-preserving case-insensitive file systems.

$ touch foo
$ pathchk -c FOO
pathchk: case conflict between filename `FOO' and existing file `foo'
$ pathchk -c bar BAR
pathchk: case conflict between filename pair `bar' and `BAR'


Because of command line length limitations, `find . -print | xargs pathchk -c' 
might not find all case conflicts, so it would be nice if pathchk could operate 
as a filter when no filenames are supplied, allowing `find . -print | pathchk 
-c'.  Which also implies that `find . -print0 | pathchk -0 -c' should work...

--
Eric Blake