You are not logged in.
What do you think of the idea of checking the Git packages once or others times a day for the version number?
don´t forgot to make a backup !
Offline
Why?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Why? Because I think it's a bit silly to have to look up old version numbers of GitHub packages in yay...
don´t forgot to make a backup !
Offline
Okay, it's just a minor flaw.
don´t forgot to make a backup !
Offline
I have a counter-question: what do you think about contacting GitHub and asking if they could send you the new version numbers whenever changes are made?
That would significantly reduce the amount of data transferred.
Last edited by Sinus-49er (2026-03-20 21:00:34)
don´t forgot to make a backup !
Offline
pkgver is stored in the PKGBUILD and .SRCINFO. There is no supported workflow where that information can be updated without a package maintainer pushing a commit. Package maintainers are also asked not to update git PKGBUILDS just because upstream has a new commit to avoid adding extra commits to the git. Imagine for a package with high commit volume how many commits per day there would be just to keep the pkgver synchronized.
Offline
only a weekend dream ...o;-D
don´t forgot to make a backup !
Offline
https://en.wikipedia.org/wiki/XY_problem
I suspect what you want to do is to compare the locally built git revision against the latest upstream commit?
Just compare those resp. see whether git pull does anything on the packages sources - this has nothing to do w/ the AUR
Offline