Package Details: telegram-desktop-dev-bin 4.11.7-2

Git Clone URL: https://aur.archlinux.org/telegram-desktop-dev-bin.git (read-only, click to copy)
Package Base: telegram-desktop-dev-bin
Description: Official desktop version of Telegram messaging app - Static binaries, developement version
Upstream URL: https://desktop.telegram.org
Licenses: GPL3
Conflicts: telegram-desktop, telegram-desktop-bin
Provides: telegram-desktop
Submitter: ItachiSan
Maintainer: ItachiSan
Last Packager: ItachiSan
Votes: 31
Popularity: 1.06
First Submitted: 2023-08-01 07:54 (UTC)
Last Updated: 2023-11-27 20:04 (UTC)

Dependencies (9)

Required by (1)

Sources (11)

Latest Comments

1 2 3 4 Next › Last »

ItachiSan commented on 2023-11-27 19:19 (UTC) (edited on 2023-11-27 19:23 (UTC) by ItachiSan)

@earch theoretically it shouldn't generate its own desktop file.

The reason why I package a desktop file is because I can guarantee people will be able to start the application, just that.

EDIT 1: I looked through the code and it seems the desktop file is generated if you select the built in updater option.

See:

https://github.com/telegramdesktop/tdesktop/blob/v4.11.8/Telegram/SourceFiles/platform/linux/specific_linux.cpp#L417

You probably want to disable that and flag the package here when it is not updated.

earch commented on 2023-11-25 21:22 (UTC)

Why do we create /usr/share/applications/telegramdesktop.desktop if Telegram creates a .desktop file on its own, when launching it?

For me it's there: .local/share/applications/org.telegram.desktop._f79d601e26a782fd149b3ffb098aae9f.desktop

So I end up with two Desktop Entries in my launcher. Btw they do differ, slightly.

xiota commented on 2023-09-20 13:18 (UTC) (edited on 2023-10-24 08:00 (UTC) by xiota)

Please remove replaces directive, in accordance with AUR submission guidelines.

ItachiSan commented on 2023-08-01 07:56 (UTC)

Hi @MarsSeed,

All has been done :) See: https://aur.archlinux.org/packages/telegram-desktop-dev-bin

Thanks for the detailed guide! Given how busy I am recently, it helped a lot.

MarsSeed commented on 2023-07-31 13:57 (UTC)

You will need to add your co-maintainer to the new package, they won't get added automatically.

MarsSeed commented on 2023-07-31 13:53 (UTC) (edited on 2023-08-01 11:55 (UTC) by MarsSeed)

It's not that complicated actually.

First you create and submit a new telegram-desktop-dev-bin package from your existing local repo.

You can do it by renaming the pkgname in your PKGBUILD, refreshing the .SRCINFO, committing these edits, and then changing the git repo's remote URL and pushing it to AUR.

git remote set-url origin ssh://aur@aur.archlinux.org/telegram-desktop-dev-bin.git
git push origin master

Then you send an AUR package merge request from the old package via the 'Submit Request' link, choosing type 'Merge', and entering the name of the new package. You can just mention in the comment that you renamed the package.

EDIT: removed the no longer existing link.

ItachiSan commented on 2023-07-31 13:23 (UTC)

Hi @MarsSeed, I can do that however I am unsure on how to do it.

MarsSeed commented on 2023-07-27 12:18 (UTC)

Please rename this package to telegram-desktop-dev-bin to conform to AUR package naming rules.

whoisroot commented on 2021-04-27 21:50 (UTC)

Please update to 2.7.3

sha256sums_x86_64=('6c698c9853b6fec513ce710123ca15f2daa0ac767a85cfd4e995c36a0b0fc088')