Package Details: ton-bin 2024.06-1

Git Clone URL: (read-only, click to copy)
Package Base: ton-bin
Description: Ultra-scalable blockchain, designed by Telegram to onboard billions of users.
Upstream URL:
Licenses: LGPL2
Submitter: neodiX
Maintainer: neodiX
Last Packager: neodiX
Votes: 0
Popularity: 0.000000
First Submitted: 2023-05-11 21:17 (UTC)
Last Updated: 2024-06-12 10:17 (UTC)

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

yochananmarqos commented on 2023-05-11 21:48 (UTC)

@neodiX: I already requested ton be merged into ton-bin.

neodiX commented on 2023-05-11 21:30 (UTC)

please delete ton repo, i created ton-bin.

neodiX commented on 2023-05-11 21:29 (UTC)

Hello reviewers, please check the latest version. Installation works as expected (pamac build ton-bin). I am not sure whether it should work as pamac install ton-bin - currently it throws - target not found: ton-bin

yochananmarqos commented on 2023-05-11 19:52 (UTC)


  • The ton package no longer exists, do not use the existing directory you had
  • Do not edit .SRCINFO manually
  • Do not use pkgbase at all, the pkgname is automatically the pkgbase
  • Remove your ton directory completely and start a fresh clone of ton-bin:
git clone ssh://

Copy your ton-bin PKGBUILD to the new ton-bin directory and initialize it:

makepkg --printsrcinfo > .SRCINFO
git commit -m "<your commit message>"
git push

neodiX commented on 2023-05-11 18:47 (UTC)

Regarding versioning, I use "latest/download" which points to the concrete release in reality. Can I use?: pkgver=latest pkgrel=1

neodiX commented on 2023-05-11 18:20 (UTC)

Hello Fabio, thank you for your comments.

1) I will leave only "Ultra-scalable blockchain, designed by Telegram to onboard billions of users." 2) got it, removing "v" 3) but there is a correlation between these binaries and gh release; 4) you mean this: source=("${pkgname}.tar.gz::")

yes, I am testing in my repo now, the final version of the source will be:

which is not one-to-one as upstream, but refers to sub-repo within the main repo. 5) not sure I got this one, could you please pinpoint some examples?

FabioLolix commented on 2023-05-11 17:28 (UTC)


  • pkgname (TON) don't have to be in pkgdesc=, 'binary artifacts' is already indicated by -bin suffix
  • prefixes don't have to be in pkgver=
  • there is no correlation between pkgver= (2023.04) and source=() (latest)
  • upstream archives are not used as source
  • renaming to ${pkgname}.tar.gz:: make this unsuitable for SRCDEST= users, instead downloads need to be non-conflicting and reusable

If you need help let me know