Bug#800771: ITP: telegram-purple -- Adds support for Telegram to libpurple
Package: wnpp
Severity: wishlist
Owner: Ben Wiederhake <BenWiederhake@gmx.de>
* Package name : telegram-purple
Version : 1.2.1~beta3-1
Upstream Author : Matthias Jentsch <mtthsjntsch@gmail.com>
* URL : https://github.com/majn/telegram-purple
* License : GPL2+
Programming Lang: C
Description : Adds support for Telegram to libpurple
This provides a libpurple plugin that allows e.g. pidgin to
use Telegram (telegram.org) as a backend.
This package is relevant, because currently users would have to choose between:
- Not using Telegram at all
- Using the official Telegram client (which is considered annoying, because
users want to keep ONE im client with ALL accounts)
- Downloading, compiling, installing directly from source (which is annoying
because that's what the debian repo is for)
I personally use it, and several friends of mine. I participated in making it
ready for Debian (e.g. cleared a GPL-violation). I will continue to use and
maintain this package, because I rely on being able to be reachable via
Telegram, and I rely on Pidgin.
There are other packages (all in RFP state) that provide similar functionality:
- "tg", which is called upstream "telegram-cli", is a CLI for communicating
with telegram. This serves the need of those who EXCLUSIVELY use telegram. I
don't fall into this group.
- "telegram", which is a RFP of the official client. Same problem: This serves
the need of those who EXCLUSIVELY use telegram. I don't fall into this group.
You might notice that tg (telegram-cli) and telegram-purple both use the same
basic library: libtgl ( https://github.com/vysheng/tgl )
You might want us to ship that package separately as a "shared library" (e.g.
"libtgl.so").
However, libtgl is in very volatile development, and upstream (= vysheng)
doesn't care much about ABI compatibility. Furthermore, it is reasonable to
assume that nobody (except those who develop both) will install telegram-cli
and telegram-purple simultaneously, so making it a shared library doesn't
really have much benefit here.
Just to reassure upstream of telegram-purple (= Matthies Jentsch) is very
willing to see telegram-purple accepted in Debian, too. ("too" because it's
already in Fedora.)
Proposed maintainers:
- Hugues Morisset (little experience in maintaining a Debian package)
- Ben Wiederhake (absolutely no experience in maintaining a Debian package)
We'd like to be co-maintainers.
If you intend to check out the source on github, please notice that this
project makes use of git submodules, and thus you need to do "git clone
--recursive https://github.com/majn/telegram-purple";
The current efforts of "debianization" can be found at:
- https://github.com/BenWiederhake/telegram-purple (branch "debian")
- https://github.com/izissise/telegram-purple (branch "debian")
Reply to: