[aur-requests] [PRQ#2239] Merge Request for telegram-purple
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/051ef01fe3962eab45b723f4ab...
Thanks!
Francisco
---
Current telegram-purple (the cloned one) PKGBUILD:
# Maintainer: Francisco Demartino
I think I rushed this merge request. Let's discuss it a bit and then
figure out what's the best. Sorry!
Transcription of telegram-purple AUR comments:
---
Comment by vinipsmaker
2015-02-04 03:32
@franciscod:
I can disown this package if you want to maintain it.
Some users want the git/development version of some package (I use
inkscape-bzr, for instance), but others want the latest stable
released version (normal packages). I didn't find the telegram-purple
package, then I "forked" the git package.
Simple as that.
---
Comment by franciscod
2015-02-04 03:40
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?
On Wed, Feb 4, 2015 at 12:25 AM,
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/051ef01fe3962eab45b723f4ab...
Thanks! Francisco ---
Current telegram-purple (the cloned one) PKGBUILD:
# Maintainer: Francisco Demartino
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/
Request #2239 has been rejected by Barthalion [1]. [1] https://aur.archlinux.org/account/Barthalion/
participants (2)
-
Francisco Demartino
-
notify@aur.archlinux.org