Package Details: telegram-purple-git 1.4.7.r2.g5a98a34-1

Git Clone URL: https://aur.archlinux.org/telegram-purple-git.git (read-only, click to copy)
Package Base: telegram-purple-git
Description: Adds support for Telegram to Pidgin, Adium, Finch and other Libpurple based messengers.
Upstream URL: https://github.com/majn/telegram-purple
Keywords: finch pidgin protocol purple telegram
Licenses: GPL
Conflicts: telegram-purple
Provides: telegram-purple
Submitter: franciscod
Maintainer: None
Last Packager: Atomisirsi
Votes: 46
Popularity: 0.000000
First Submitted: 2014-10-27 18:59 (UTC)
Last Updated: 2022-03-31 07:38 (UTC)

Pinned Comments

Atomisirsi commented on 2021-01-07 15:56 (UTC)

Development of this plugin is discontinued in favor of Telegram tdlib.

This PKGBUILD remains for usage of the master branch.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

flu commented on 2015-04-15 11:12 (UTC)

Oh my.. Yes "package", exactly.

franciscod commented on 2015-04-15 03:50 (UTC)

Hi flu! Did you mean s/prepare/package/ ? I'll look at it. Thanks!

flu commented on 2015-04-14 21:30 (UTC)

The "prepare" function should be called "build" and a separate "prepare" should include only the proper cd and the make install. Best regards.

franciscod commented on 2015-02-08 21:35 (UTC)

@vinipsmaker: Okay! I'll file a merge request. Thanks for your help!

vinipsmaker commented on 2015-02-08 21:33 (UTC)

@franciscod: Okay, I disowned the package. Feel free to do whatever you want. I think I'll myself use the -git package, now that I understand the master branch policy from telegram-purple repo.

franciscod commented on 2015-02-08 21:28 (UTC)

I think a merge is appropiate. It seems the correct naming is -git, so we should merge telegram-purple into telegram-purple-git, right? Obrigado :)

vinipsmaker commented on 2015-02-08 21:12 (UTC)

@franciscod: What I found of relevant: "Package versions should be the same as the version released by the author. Versions can include letters if need be (eg, nmap's version is 2.54BETA32). Version tags may not include hyphens! Letters, numbers, and periods only." -- https://wiki.archlinux.org/index.php/Arch_packaging_standards#Package_naming "Suffix pkgname with -cvs, -svn, -hg, -darcs, -bzr, -git etc. unless the package fetches a specific release." -- https://wiki.archlinux.org/index.php/VCS_package_guidelines#Guidelines Reading a little more on the page <https://wiki.archlinux.org/index.php/VCS_package_guidelines>, I think I should drop this package and your package should be the only one maintained. What do you think?

vinipsmaker commented on 2015-02-04 04:34 (UTC)

@franciscod: I wasn't aware about the telegram-purple development process. It's a clever trick to use this information to ease the PKGBUILD maintaince. I'll read about ArchLinux packaging practices again. Maybe I'll find something useful.

franciscod commented on 2015-02-04 03:40 (UTC)

Thanks for your explanation! I'm ashamed of my initial hostile reaction, I felt like my work being copied and didn't like it (dammit, ego!). Sorry! At upstream, the development happens on feature branches. The master branch points to the latest stable tagged version (also, your package points to v0.6, and the latest one is v0.6.1) so we'd supporting the exact same version! https://github.com/majn/telegram-purple/tags https://github.com/majn/telegram-purple/branches Maybe the best way of joining forces is merging both packages and sharing the maintain process on github. What do you think?

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »