Subject: [alpine-aports] [PATCH] testing/telegram-desktop: drop maintainership

From: Alex Raschi <[email-masked]>
Date: Sun, 12 May 2019 14:07:51 +0200

the aport has been rewritten and now uses an unofficial third party build
system that i don't want to maintain
---
 testing/telegram-desktop/APKBUILD | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/testing/telegram-desktop/APKBUILD b/testing/telegram-desktop/APKBUILD
index d951cff246..77770120c5 100644
--- a/testing/telegram-desktop/APKBUILD
+++ b/testing/telegram-desktop/APKBUILD
@@ -1,4 +1,4 @@
-# Maintainer: Alex Raschi <[email-masked]>
+# Maintainer:
 # Contributor: Leo <[email-masked]>
 pkgname=telegram-desktop
 pkgver=1.6.7
-- 
2.21.0

---
Unsubscribe:  [email-masked]
Help:         [email-masked]
---

---

From: Kevin Daudt <[email-masked]>
Date: Sun, 12 May 2019 18:47:34 +0200

Sad to here this.

It was necessary because the build was failing and only a limited amount
of people have access to create snapshots and upload them to dev.

We prefer being able to build packages without having to create archives
ourselfs. It just happened that this PR was already available so that
was the quickest way to get things building again.

If you know a way to use the official build system but not having to
rely on creating snapshots, we're happy to use that.

Kind regards, Kevin.

---

---

From: Alex Raschi <[email-masked]>
Date: Sun, 12 May 2019 19:20:05 +0000

Hi Kevin,

I didn't know about the snapshots situation and i understand the issues of
uploading archives.

Yes there is an another way to avoid creating a snapshot but as you can see
in
the committed change, it requires keeping track of additional dependencies
manually which involves of checking git hashes every time.

That's why the aport used snapshots and i opted for this solution when i
wrote
it, with git submodules is a lot easier.

Rewriting aport without any sort of advise to the maintainer should be
avoided
in my opinion, i found it rewritten without knowing anything since i don't
use
github and the patch comes from there.

The new build seems to require to update the source file lists with every
new
update too, and this doesn't seem to me a good change. Let just clone gyp
with
another archive then, rather than using something not supported upstream if
possible.

Anyway i am a little busy lately so if there is someone that would maintain
better the package then ok, i don't mind that. I can't hide the fact that
the
previous commit pissed me off a little...

Cheers, Alex.