Closed alllexx88 closed 6 months ago
However, there's no update/default.sh in the current version, so I don't understand how to create custom upgrade scripts, and where to put them.
The readme is out-of-date but I still don't have time to update it now. Sorry.
We still have this mechanism to override the upgrade script. As shown in https://github.com/arch4edu/aur-auto-update/blob/main/.github/workflows/build.yml#L102, if there is a file named pkgbase.override
, then it will be used to replace bin/update-pkgver
.
This mechanism is some sort of unsafe. Please only use it when it's truely necessary.
Thank you for your reply @petronny , I appreciate it!
Hi,
README.md
saysHowever, there's no
update/default.sh
in the current version, so I don't understand how to create custom upgrade scripts, and where to put them.I was thinking how to configure the auto update bot for an AUR package like telegram-desktop-dev-bin. We can get the latest release (including pre-releases) with a regex:
This is better than using a github source like this:
(since potentially a release could not have a linux binary, like when 4.14.15 has only a linux binary)
However, getting the latest version is not enough, since source url is different for beta releases:
https://github.com/telegramdesktop/tdesktop/releases/download/v${pkgver}/tsetup.${pkgver}.beta.tar.xz
vshttps://github.com/telegramdesktop/tdesktop/releases/download/v${pkgver}/tsetup.${pkgver}.tar.xz
and we also need to set
_dev=1
in thePKGBUILD
for a beta realease, and to something else, like_dev=0
, for stable releases: PKGBUILD.I think this can easily be tested with a
grep
overhttps://api.github.com/repos/telegramdesktop/tdesktop/releases
content, but the bot would require a custom upgrade script to set the variable accordingly.I'm not the maintainer of this package, but I'm curious if it's doable, and how?
Thanks :smiley: