[aur-requests] [PRQ#2239] Merge Request for telegram-purple
notify at aur.archlinux.org
notify at aur.archlinux.org
Wed Feb 4 03:25:19 UTC 2015
franciscod [1] filed a request to merge telegram-purple [2] into
telegram-purple-git [3]:
TL;DR: cloned package, the other guy never contacted me. wat do?
dedup?
This package is a clone of my original telegram-purple-git repo, with
minor differences. I don't know if that's not wanted on AUR, I don't
care of the submitter copying my work, I just think that it's better
to have all users using a single package for better support and
bugfixing. My package also has 18 votes, while this has 4.
Its PKGBUILD even contains my name! I've never been contacted by
vinipsmaker (pkg submitter). Here's an old version of my package's
PKGBUILD:
https://github.com/franciscod/aur-franciscod/blob/051ef01fe3962eab45b723f4abea3500895a6967/telegram-purple-git/PKGBUILD
Thanks!
Francisco
---
Current telegram-purple (the cloned one) PKGBUILD:
# Maintainer: Francisco Demartino <demartino.francisco at gmail.com>
pkgname=telegram-purple
pkgver=0.6
pkgrel=2
pkgdesc="Adds support for Telegram to Pidgin, Adium, Finch and other
Libpurple based messengers."
arch=('i686' 'x86_64')
url="https://github.com/majn/telegram-purple"
license=("GPL")
makedepends=("git")
depends=('glib2' 'openssl' 'libpurple' 'zlib')
source=("git+https://github.com/majn/telegram-purple#tag=v${pkgver}"
"0001-Bugfix-always-respect-DESTDIR-in-Makefile.patch")
sha512sums=('SKIP'
'82c137913b121c615e172d105df1ca76dcbc3834f07cad7337e08fb2b73e164baa565c6e91ab603769aed87efec01c4901c2f1b8a534a19f2f72cd3487cff269')
prepare() {
cd "${srcdir}/${pkgname}"
git submodule update --init --recursive
patch -p1 <
"${srcdir}/0001-Bugfix-always-respect-DESTDIR-in-Makefile.patch"
}
package() {
cd "${srcdir}/${pkgname}"
./configure
make DESTDIR="$pkgdir/"
make DESTDIR="$pkgdir/" install
}
[1] https://aur.archlinux.org/account/franciscod/
[2] https://aur.archlinux.org/pkgbase/telegram-purple/
[3] https://aur.archlinux.org/pkgbase/telegram-purple-git/
More information about the aur-requests
mailing list