Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Felix Miata
Reindl Harald composed on 2017-11-20 18:50 (UTC+0100): > what do you gain from uppercase chars in filenames? 1-unpredictable location in a sorted filename list 2-need for case-insensitivity switches to various shell and script commands 3-many additional opportunities to mistype long unpronounceab

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Thiago Macieira
On segunda-feira, 20 de novembro de 2017 09:59:10 PST Reindl Harald wrote: > you missed "what do you gain from uppercase chars in filenames?" Why should we constrain ourselves to lowercase? We've had uppercase library names for over 12 years (starting with Qt 4.0). And that's not including libX1

[ANNOUNCE] CMake 3.10.0 available for download

2017-11-20 Thread Robert Maynard
I am proud to announce that CMake 3.10.0 is now available for download at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.10 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.10/release/3.10.html Some of the mor

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Reindl Harald
Am 20.11.2017 um 18:55 schrieb Brüns, Stefan: On Montag, 20. November 2017 18:50:34 CET Reindl Harald wrote: Am 20.11.2017 um 18:30 schrieb Thiago Macieira: On segunda-feira, 20 de novembro de 2017 07:58:06 PST Reindl Harald wrote: hopefully this means also that filenames in the future don't

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Brüns , Stefan
On Montag, 20. November 2017 18:50:34 CET Reindl Harald wrote: > Am 20.11.2017 um 18:30 schrieb Thiago Macieira: > > On segunda-feira, 20 de novembro de 2017 07:58:06 PST Reindl Harald wrote: > >> hopefully this means also that filenames in the future don't contain > >> uppercase chars > > > > Why

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Reindl Harald
Am 20.11.2017 um 18:30 schrieb Thiago Macieira: On segunda-feira, 20 de novembro de 2017 07:58:06 PST Reindl Harald wrote: hopefully this means also that filenames in the future don't contain uppercase chars Why would we want that? well, i don't know many projects or people which create bi

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Thiago Macieira
On segunda-feira, 20 de novembro de 2017 07:58:06 PST Reindl Harald wrote: > hopefully this means also that filenames in the future don't contain > uppercase chars Why would we want that? -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Sour

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Kevin Funk
On Monday, 20 November 2017 16:50:58 CET Harald Sitter wrote: > Guten Abend Everyone! > > To aid with use of our tarballs on Windows and case-insensitive file > systems, releaseme now makes sure [1] that the tarballs it generates > are safe to use in such contexts. Thanks for helping out on that

Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Reindl Harald
Am 20.11.2017 um 16:50 schrieb Harald Sitter: Guten Abend Everyone! To aid with use of our tarballs on Windows and case-insensitive file systems, releaseme now makes sure [1] that the tarballs it generates are safe to use in such contexts. As this is a major problem for pretty much every sour

releaseme new requirement: non-conflicting files on case-insensitive FS/OS

2017-11-20 Thread Harald Sitter
Guten Abend Everyone! To aid with use of our tarballs on Windows and case-insensitive file systems, releaseme now makes sure [1] that the tarballs it generates are safe to use in such contexts. As this is a major problem for pretty much every source tarball as it prevents people from doing Window