> Am 30.09.2016 um 09:53 schrieb Ryan Schmidt <ryandes...@macports.org>: >> Apple could (and IMHO should) have made case-sensitivity the default and let >> everyone come to term with the fact that foo and Foo are not the same thing >> (or add normalising glue code in their highlevel APIs).
> Apple has decided Mac OS has a case-insensitive filesystem by default; it's > pointless to talk about what you think they should have done; they didn't do > that. Past/presence. But: Apple seems finally to go into case-sensitive per default resp. case-sensitive-only: Apples forthcoming APFS is/will be case sensitive per default, and relating Sierra so far is case sensitive-only (when, if at all case-insensitivity will be implemented, only Apple knows): Apple Developer Library: Apple File System Guide: FAQ: Compatibility https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html#//apple_ref/doc/uid/TP40016999-CH6-DontLinkElementID_1 [quote] Q: What are the limitations of Apple File System in macOS Sierra? A: […] ° Case Sensitivity: Filenames are case-sensitive only. […] [/quote] ars technica (6/13/2016): Digging into the dev documentation for APFS, Apple’s new file system http://arstechnica.com/apple/2016/06/digging-into-the-dev-documentation-for-apfs-apples-new-file-system/ [quote] Perhaps most importantly, the file system currently is case-sensitive, and this cannot be disabled. HFS+ breaks with most Unix-y file systems in that it can be configured to not use case sensitivity; in fact, running OS X—ahem, macOS, sorry—with case-sensitive HFS+ can lead to its own problems. But, for now, if you want to use APFS, you’re going to do so on a non-startup volume, and you’re going to have to deal with case sensitivity. [/quote] Sierk Bornemann _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
