Package: wnpp Severity: wishlist Owner: Mike Gabriel <mike.gabr...@das-netzwerkteam.de> X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name : td1.8.11 Version : 1.8.11~git20241021.3179d35+dfsg Upstream Contact: https://github.com/tdlib/td * URL : https://core.telegram.org/tdlib * License : BSL-1.0 Programming Lang: C++ Description : telegram database library (development headers, API/ABI v1.8.11) TDLib (Telegram Database Library) is a cross-platform, fully functional Telegram client. This library helps third-party developers create their own custom apps using the Telegram platform. . In Debian, we already have an src:pkg td containing the (sort-of) latest version of the telegram database library (currently 1.8.38, 1.8.42 will be uploaded soon). . In Lomiri's TELEports app we face the problem that TELEports is based on td 1.8.11 (the version shipped in this to be uploaded src:pkg). The situation around tdlib is special, because tdlib developers change their API with every release and a certain app, developed on top of a certain tdlib version is pinned to this API version until the app gets forwarded ported. . As lomiri-teleports-app sort of works, but not 100% (replies are not shown properly, message forwardings and message replies are not possible due to missing buttons in the UI), we tried building lomiri-teleports-app against tdlib 1.8.11 (as bundled in TELEports upstream) and those issues are gone. Thus, we (Debian UBports Packaging Team) have come up with the plan to make tdlib co-installable in various versions, so that consumers of tdlib (i.e. apps using that library) can ship their own version in Debian. . The other option would have been bundling tdlib in the lomiri-teleports-app src:pkg (like done upstream for Snap and Click packaging), but we wanted to avoid hiding an older version of tdlib in the lomiri-teleports-app src:pkg. Instead, we provide it via its own shared library src:pkg. . For more details, see: https://github.com/tdlib/td/issues/2696#issuecomment-2037015283 https://github.com/tdlib/td/issues/2696#issuecomment-2293886265 . Please provide feedback on this and the chosen strategy, if you have any (diverging) opinion on this. Thanks!
