Package Details: ayugram-desktop 5.12.3-6

Git Clone URL: https://aur.archlinux.org/ayugram-desktop.git (read-only, click to copy)
Package Base: ayugram-desktop
Description: Desktop Telegram client with good customization and Ghost mode.
Upstream URL: https://github.com/AyuGram/AyuGramDesktop
Keywords: anti-recall ayugram telegram
Licenses: GPL-3.0-only
Submitter: ZhangHua
Maintainer: ZhangHua
Last Packager: ZhangHua
Votes: 12
Popularity: 2.13
First Submitted: 2023-11-06 01:05 (UTC)
Last Updated: 2025-04-05 03:17 (UTC)

Dependencies (46)

Required by (0)

Sources (40)

Latest Comments

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

ZhangHua commented on 2024-10-07 04:49 (UTC)

@oldman33 I checked their tarball, and I found that there is only one executable file /home/gentoo/Downloads/ayugram/ayugram-desktop in it and does not found some libraries like protobuf in ldd's outputs, it must be that they static linked everything possible, include protobuf, so I think you can run this file directly on archlinux. You can run bsdtar -xpf /path/to/ayugram.tar.gz to unpack it and get the executable.

As for the differences between those three packages, you can continue reading contents below:

TL;DR: Channel version and ayugram-desktop-bin are prebuilt versions. This package is built from source.

Detailed explaination: The tarball in channel is built by someone I do not know. ayugram-desktop-bin is repacked from andontie AUR's prebuilt version. Neither of what I can guarantee is safe. ayugram-desktop is completely built by yourself, you download source code and use compiler to get a working executable file. I just provide an automation script to build it. As for it safety, I think it may be better than those versions mentioned before because everything can be audited by yourself. Because channel version and ayugram-desktop-bin are prebuilt version, you do not need a lot of resource to build from source like this package, but prebuilt versions may not be suitable for your distribution. For example, I saw your distribution is ArcoLinux, while aur is designed for ArchLinux, if your distribution cannot follow ArchLinux's upgrades, like protobuf is upgraded after ArchLinux's upgrades for some hours to days, or to even weeks, you may meet that protobuf's so is missing during this period of time. Because prebuilt version links to a newer protobuf on ArchLinux but your distribution has not upgraded it.

If you are curious why I use protobuf as example, that's because protobuf usually changes its so's names when upgrades and breaks a lot of program depends on it, like ayugram-desktop. We have to rebuild those affected programs against upgraded protobuf. Thankfully it does not upgrade too frequent.

oldman33 commented on 2024-10-07 02:22 (UTC)

@ZhangHua thank, i tried ayugram-desktop-bin and seem it work, although I had to remove DESKTOPINTEGRATION=1 in the shortcut for it to run. i found in ayugram telegram channel build ayugram.tar.gz 87.3Mb, Any Linux build v5.4.1, not for PotnieYaicaOS. don't know how to try to run it on Arch Sorry if I'm asking a basic question, but what's the difference between those 3? The do not rebuild for protobuf upgrades build (from their telegram channel), the ayugram-desktop-bin build, and the build from AUR

ZhangHua commented on 2024-10-05 05:53 (UTC)

@oldman33 Maybe you can check their telegram channel, someone built ayugram for linux and packaged as a tarball. But it seems that they do not rebuild for protobuf upgrades, so I doubt if you can run the prebuilt binary directly on your system. What's more, you can try ayugram-desktop-bin, it is just a repackage script for a prebuilt version of ayugram so you don't need to build ayugram yourself.

oldman33 commented on 2024-10-05 03:14 (UTC) (edited on 2024-10-05 03:14 (UTC) by oldman33)

@ZhangHua , It seems too much for me, Ayugram on Linux is harder than I thought. Each person has to build for himself

ZhangHua commented on 2024-10-05 01:56 (UTC)

@oldman33 Find makepkg.conf used for building, typically it should be /etc/makepkg.conf, find OPTIONS variable, you will find a lto in it, change it to !lto. This will disable makepkg adding lto flags, but cannot prevent if upstream project add lto flags. This will also change all packages use this makepkg.conf to build, if you just want to disable lto for this package, you can also choose setting options=(!lto) in the PKGBUILD.

oldman33 commented on 2024-10-05 01:20 (UTC)

@vitaliikuzhdin how to disable LTO, and others way? im a newbie on Arch!

ZhangHua commented on 2024-10-05 00:18 (UTC) (edited on 2024-10-05 00:31 (UTC) by ZhangHua)

@oldman33 No, at least I can't give any advice without knowing the actual command called by cmake. You can set VERBOSE=1 in environment to let cmake print what it calls. See here for more info.

I have changed build tool from ninja to make, so it should use 1 core without -j arguments set. As for LTO, I am not sure if it is needed to disable it because I am not familiar with ArcoLinux.

According to gcc's code, it seems that something happens when write arguments to a temp file, you may check if your /tmp has enough space, maybe you can set TMPDIR=/path/to/another/place to use a larger temp directory.

oldman33 commented on 2024-10-04 22:13 (UTC) (edited on 2024-10-04 22:13 (UTC) by oldman33)

@ZhangHua, i tried change swap to 32G and same 8G Ram seem previous issue gone. Cant believe it requires many storage space like that: i much moved some data to other to have 40G space for build. But new issue now : https://ibb.co/3Nx4PRY

Any advice please?

ZhangHua commented on 2024-10-04 05:27 (UTC)

@oldman33 I think no need to change code. This package is tested with makechrootpkg command in devtools, so I think there should be no missing dependencies in PKGBUILD.

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