Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
On Tuesday, 21 November 2017 14:24:04 CET Felix Miata wrote: > Sven Brauch composed on 2017-11-21 12:25 (UTC+0100): > > Felix Miata wrote: > >> Case sensitive filesystems are one of the most annoying things about > >> FOSS. > > > > I'd count that as a win. > > InsaniTY > INSaniTy > InSAnItY > inSANity > INsANItY > INSANiTY > iNSaNiTy > InsAnItY > > Boss: Worker, please get me the insanity file. > > Worker: which one Boss? > > Boss: The one spelled I N S A N I T Y! > > Worker: There's at least 8 spelled that way! > > Boss: How is that possible? > > Worker: A & a sound the same, B & b sound the same, C & c sound the same, ad > nauseum. There's no rhyme or reason for the case differences. It's > anarchistic. *yawn*. Really, that discussion is completely moot. -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
Sven Brauch composed on 2017-11-21 12:25 (UTC+0100): > Felix Miata wrote: >> Case sensitive filesystems are one of the most annoying things about FOSS. > I'd count that as a win. InsaniTY INSaniTy InSAnItY inSANity INsANItY INSANiTY iNSaNiTy InsAnItY Boss: Worker, please get me the insanity file. Worker: which one Boss? Boss: The one spelled I N S A N I T Y! Worker: There's at least 8 spelled that way! Boss: How is that possible? Worker: A & a sound the same, B & b sound the same, C & c sound the same, ad nauseum. There's no rhyme or reason for the case differences. It's anarchistic. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
On Dienstag, 21. November 2017 12:25:56 CET Sven Brauch wrote: > On 21/11/17 03:53, Felix Miata wrote: > > Case sensitive filesystems are one of the most annoying things about FOSS. > > I'd count that as a win. +1, and they existed long before FOSS was around. p.s. The footer below is selected purely random - what coincidence -- Regards Thomas Baumgart https://www.telegram.org/ Telegram, the better WhatsApp - MicroSoft Windows - from the people who brought you edlin - signature.asc Description: This is a digitally signed message part.
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
On 21/11/17 03:53, Felix Miata wrote: > Case sensitive filesystems are one of the most annoying things about FOSS. I'd count that as a win. signature.asc Description: OpenPGP digital signature
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 unpronounceable, immemorable strings Case sensitive filesystems are one of the most annoying things about FOSS. :-( -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 libX11, libGL, libGLES, libGLU, libICE, libSM... -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 contain uppercase chars Why would we want that? well, i don't know many projects or people which create binaries other than lowercase chars and using only lowercase filenames would avoid the whole topic at it's root to be honest: i am annyoed that "lsof | grep DEL | grep /usr" brings OUCH! Fixed that for you: lsof | grep -E "\sDEL\s.*\s/usr" you missed "what do you gain from uppercase chars in filenames?"
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 would we want that? > > well, i don't know many projects or people which create binaries other > than lowercase chars and using only lowercase filenames would avoid the > whole topic at it's root > > to be honest: i am annyoed that "lsof | grep DEL | grep /usr" brings OUCH! Fixed that for you: lsof | grep -E "\sDEL\s.*\s/usr" Regards, Stefan
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 binaries other than lowercase chars and using only lowercase filenames would avoid the whole topic at it's root to be honest: i am annyoed that "lsof | grep DEL | grep /usr" brings always these KDE processes for a long time what do you gain from uppercase chars in filenames?
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 Source Technology Center
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 front! Regards, Kevin > As this is a major problem for pretty much every source tarball as it > prevents people from doing Windows builds and/or unpack on exfat/fat32 > this is considered a fatal flaw in the tarball. To that end if you use > releaseme you may want to run tarme now so your next release doesn't > get held up by case-insensitive file conflicts. > > If you have any questions please do ask. > > [1] > https://phabricator.kde.org/R572:0936ab0e02551fe6d3e8ad07b97cd7d7d3d26838 > > HS -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 source tarball as it prevents people from doing Windows builds and/or unpack on exfat/fat32 this is considered a fatal flaw in the tarball. To that end if you use releaseme you may want to run tarme now so your next release doesn't get held up by case-insensitive file conflicts. If you have any questions please do ask. [1] https://phabricator.kde.org/R572:0936ab0e02551fe6d3e8ad07b97cd7d7d3d26838 hopefully this means also that filenames in the future don't contain uppercase chars [root@rh:~]$ lsof | grep DEL | grep /usr konqueror 8058 harry mem REG9,1 26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0 QXcbEvent 8058 8059 harry mem REG9,1 26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0 QDBusConn 8058 8060 harry mem REG9,1 26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0 QThread8058 8061 harry mem REG9,1 26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0 konqueror 23596 harry mem REG9,1 26315841444562 /usr/lib64/libKF5KDELibs4Support.so.5.38.0
releaseme new requirement: non-conflicting files on case-insensitive FS/OS
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 Windows builds and/or unpack on exfat/fat32 this is considered a fatal flaw in the tarball. To that end if you use releaseme you may want to run tarme now so your next release doesn't get held up by case-insensitive file conflicts. If you have any questions please do ask. [1] https://phabricator.kde.org/R572:0936ab0e02551fe6d3e8ad07b97cd7d7d3d26838 HS
