"Dmitrij D. Czarkoff" <[email protected]> wrote: >I have to use Telegram these days, so I had a look into Cutegram. This >port is outdated, and does not support many of the features that were >recently introduced into Telegram. I prepared an update to see whether >it would improve the situation, and frankly it does not. > >The story becomes a bit more complicated here. Cutegram is supposed to >be in the middle of transition to pure QML application with 3 C++ >libraries providing the protocol support and some UI stuff. That is >supposed to be ultimately released as Cutegram 3.0. I say "supposed", >because the last substantial commit to the repo was made in 2016, and >the latest release of QML branch was an early alpha a year ago. 2.x >branch is officially discontinued after 2.7.1 release, which happens to >be the last stable release of Cutegram to date. > >In my opinion, Cutegram does not support enough functionality to be >worth maintenance burden. Provided that development of the application >dried up, I believe that both net/cutegram and its dependency >devel/libqtelegram-aseman-edition should be removed. Alternatively, >these ports may be updated to the latest (last?) stable versions. The >diffs, and a port of a new dependency of Cutegram - TelegramQML - are >attached. > >Regardless the future of Cutegram and its port, I still need a working >and sufficiently feature-complete Telegram client, so a port of >telegram-purple (a protocol plugin for Pidgin) is also attached. > >Comments? OKs?
ping
