[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#833793: ITP: telegram-purple -- Adds support for Telegram to libpurple

Package: wnpp
Severity: wishlist
Owner: Ben Wiederhake <BenWiederhake.GitHub@gmx.de>

* Package name    : telegram-purple
  Version         : 1.3.0
  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, cleaned up the build system).
I will continue to use and maintain this package, because I rely on being
able to be reachable via Telegram via 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.
- Note that this is a resurrection of #800771, as it timed out.

You might notice that tg (telegram-cli) and telegram-purple both use the same
basic library: libtgl ( https://github.com/vysheng/tgl )
It is not meaningful to ship that package separately as a "shared library"
"libtgl.so").  The rationale for this and other packaging choices can be
found in `debian/README.source`.

Just to reassure: upstream of telegram-purple (= Matthias Jentsch) is very
willing to see telegram-purple accepted in Debian.

Proposed maintainers:
- Ben Wiederhake (absolutely no experience in maintaining a Debian package)

If you intend to check out the source on GitHub, please notice that this
project makes use of git submodules *within* 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 this branch:

You might notice that 1.3.0 isn't released yet -- that's because it truely
isn't.  However, it's stable, and they/we are about to release, and I think
there's nothing essential missing in `debian/`, so I might be able to RFS
within a day after release of 1.3.0.


Reply to: