On Sun, 20 Jan 2019, Adam Borowski wrote: > Simple setups still work in Buster, but it's easy to run into > something that doesn't. That'd be a nasty surprise for the user, thus > it's better to make the break faster and more obvious. Then, pretty > surely even such simple setups won't work in Bullseye.
That’s completely backwards. I’d expect people with such setups to report in when they have any problems (perhaps even on unstable, but I know the corporate world), but if things work for them, they don’t need to, and if they break they’ll notice that on their test setup (hopefully) and can act appropriately. By keeping the officially unsupported thing possible we’re sen‐ ding a signal that patches to fix what was accidentally broken are welcome, even for officially unsupported scenarios that need a little local admin love to work. (Incidentally, I was very angry at the bash/dash maintainers when they broke the old way to use mksh as /bin/sh, which was rather easy, by changing the way the diversions and symlinks were distributed. And Policy actually does support running a system with lksh (from the mksh package) as /bin/sh…) I like the “my beautiful little paradise” analogy and postu‐ late that many experienced Debian users have those little paradises of their own, which is why I’m going to continue to push for freedom of choice, and upstreaming as much of that as possible so that that freedom of choice is not only in theory possible but also practical (from amount of devia‐ tions from stock needed). Thanks for listening, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die!
