Arch Linux User Repository

I'm not sure if it's useful to stat a file that you just downloaded... won't the creation date just be the download date (which was just a second ago)? Instead I'd suggest using a plain pkgver() like

pkgver() {
    date +'%Y%m%d'
}

And the idea of using pkgver() is not that you as a maintainer create any more releases of the package, but that the package version string is set during build-time.

So if you had released aacs-keydb-20250101 and I'm installing your package today I'd build and install aacs-keydb-20250511.

The advantage is that different builds of aacs-keydb from different dates will then actually reflect the fact that the underlying keydb.cfg is not the same. Currently, all your users have aacs-keydb-1.0-1 installed, but all of them have different contents in the package.

Also, if I rebuild the package at a later date, I'll get a new package version and archive file, like aacs-keydb-20251201. So the old package that I built before isn't overwritten, but still in the cache.

And if you the maintainer want to release an important change, you can just bump the version to todays date, and thereby trigger yay or whatever to recognize the update, no matter what version your users had installed before.

It really makes a lot of sense to use here.

See more in the Arch Wiki

The key database changes way too often. I think it would be better that you just use the installed version as long as it works (because of the revocation table in your bluray player) and if it does not work anymore, then you can just type "yay -S aacs-keydb" to update it.

A suggestion: to keep the version number useful, add

pkgver() {
        # Use this if file time is correct accounting for time zones
        # date +'%Y%m%d.%H%M%S' -u -d "@$(stat -c '%Y' "${srcdir}/keydb.cfg")"
        date +'%Y%m%d.%H%M%S' -d "$(stat -c '%y' "${srcdir}/keydb.cfg")"
}

to make the version number be the date and time of the latest update to the file (and then run makepkg -od to update the version number at least once).

Note that, as long as you extract the zip file in the same time zone as you run the pkgver function, this should usually give you the same time as on the FindVUK web page, but this is not going to be the correct time in either UTC or your localtime. It is in theory possible to fix that, but it probably isnʼt worth it. I included the change necessary in the pkgver function for that, but not a corresponding prepare function to make it work