On 2021/05/05 15:34, Omar Polo wrote: > Hello, > > Please find attached net/tdlib. It's required by another port I'm going > to submit (net/tg), and it will also come in handy for the fellow emacs > users (telega.el depends on net/tdlib; unfortunately I can't make a port > for it because it depends on various other stuff on MELPA.) > > Since I've been using this for a year or so, I'd also like to take > MAINTAINER. > > $ pkg_info tdlib > Information for inst:tdlib-1.7.3 > > Comment: > cross-platform library for building Telegram clients > > Required by: > py3-telegram-0.14.0 > > Description: > TDLib (Telegram Database Library) is a cross-platform, fully > functional Telegram client that can be easily used from almost any > programming language.
upstream has "TDLib (Telegram Database library) is a cross-platform library for building Telegram clients" which sounds more accurate? > WWW: https://github.com/tdlib/td how about https://core.telegram.org/tdlib ? : # XXX: because of GH_COMMIT : PKGNAME = tdlib-1.7.3 : DISTNAME = tdlib-${GH_COMMIT} : : GH_ACCOUNT = tdlib : GH_PROJECT = td : #GH_TAGNAME = v1.7.0 # XXX: keep in sync with COMMIT below : GH_COMMIT = 9964d24ec8e03bd0bc4d5fe33438f056d133fc1a bit messy; where does 1.7.3 come from? is there a need to use these development versions rather than an actual release? https://github.com/tdlib/td/issues/1243 : COMMIT = 9964d24ec8e03bd0bc4d5fe33438f056d133fc1a : SUBST_VARS += COMMIT if the development versions are needed, this should reuse GH_COMMIT rather than a separate var with the same contents.
