diff options
| author | A. Wilcox <AWilcox@Wilcox-Tech.com> | 2022-07-03 17:12:43 -0500 |
|---|---|---|
| committer | Zach van Rijn <me@zv.io> | 2022-10-21 18:34:02 -0500 |
| commit | 9ac6bc00a1563dc270d2464054709bdfd0592af0 (patch) | |
| tree | 4de9184024cc83be041c79ce0b1acf4da9448e7d | |
| parent | 8a240ed95da6e3299fd0542d2799499866080494 (diff) | |
| download | packages-9ac6bc00a1563dc270d2464054709bdfd0592af0.tar.gz packages-9ac6bc00a1563dc270d2464054709bdfd0592af0.tar.bz2 packages-9ac6bc00a1563dc270d2464054709bdfd0592af0.tar.xz packages-9ac6bc00a1563dc270d2464054709bdfd0592af0.zip | |
user/telegram: Move to legacy/
Big-endian support never landed, which takes out two architectures.
Telegram never built properly on ARMv7, which takes out another one.
This violates our policy of packages in user/ being available for a
minimum of 5 of 6 architectures unless it is a system-specific package.
Additionally, there have been internal disagreements on how to approach
handling of the API key material.
On the personal side, I don't have a lot of time to chase upstream, and
I don't want to ship something potentially security-sensitive in such a
state.
| -rw-r--r-- | legacy/telegram/APKBUILD (renamed from user/telegram/APKBUILD) | 0 | ||||
| -rw-r--r-- | legacy/telegram/endian.patch (renamed from user/telegram/endian.patch) | 0 | ||||
| -rw-r--r-- | legacy/telegram/rlottie.patch (renamed from user/telegram/rlottie.patch) | 0 |
3 files changed, 0 insertions, 0 deletions
diff --git a/user/telegram/APKBUILD b/legacy/telegram/APKBUILD index 46cc4a9c1..46cc4a9c1 100644 --- a/user/telegram/APKBUILD +++ b/legacy/telegram/APKBUILD diff --git a/user/telegram/endian.patch b/legacy/telegram/endian.patch index 40a3b4478..40a3b4478 100644 --- a/user/telegram/endian.patch +++ b/legacy/telegram/endian.patch diff --git a/user/telegram/rlottie.patch b/legacy/telegram/rlottie.patch index 6bd2ff6c3..6bd2ff6c3 100644 --- a/user/telegram/rlottie.patch +++ b/legacy/telegram/rlottie.patch |