Telegram Desktop retirement notice from RPM fussion(lists.rpmfusion.org)
lists.rpmfusion.org
Telegram Desktop retirement notice from RPM fussion
https://lists.rpmfusion.org/archives/list/[email protected]/thread/5A7MRE3BG66PQXSP263FUZ7XS5PMDNUV/
8 comments
Ignore packagers requests for help, then bash them for packaging wrong.
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.
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.
I’m not sure if their position could be any clearer: they can’t stop you re-packaging it, but it’s totally unsupported. Only the official builds are supported.
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.
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.
> "We only support static builds, if you need shared -> fix it
yourself"
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"
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"
I don't know how the situation is on RPM-based systems, but I've been using the same telegram binary on arch as well as debian stable, with no complaints. Having maintained deb/rpm packages in the past, I won't shame anyone for being annoyed towards those ecosystems.
I use Pidgin as client for Telegram. I use Pidgin since ICQ.
https://github.com/telegramdesktop/tdesktop/issues/8769#issu...