Telegram Desktop retirement notice from RPM fussion(lists.rpmfusion.org) |
Telegram Desktop retirement notice from RPM fussion(lists.rpmfusion.org) |
https://github.com/telegramdesktop/tdesktop/issues/8769#issu...
You know, F those guys. I see no excuse for Telegram being so uncooperative. The points in this frankly embarassing little comment don't constitute an excuse to ignore every other perfectly valid attempts to interoperate with them.
Being granted that most noble of OSS titles, imbued by the ghost of Dennis Ritchie himself, the rank of packager in actuality means jack-all and doesn’t give your requests any more weight or mean that they need to answer them at all. They don’t want it packaged like that.
They publish and support static binaries. Anything else is a burden, and they shouldn’t adapt their project because someone actually wants to dynamically link it.
I think this is thecause and effect why below
> recently they removed builds support against Qt < 5.15.
Maintaining backward compatibility needs a lot of work, especially ".so dependency hell"