Not sure what you mean by ‘invoked’, but the way I understand it works for the AUR is that by defining the
PKGBUILD file with the available distributions on the Github repo, a user can download the required files for themselves and build the binary on their machine as I did.
The only issue I had was how to point to the correct release on Github. I could specifically point to the package ‘master’, but I used the hotfix 0.6, as it was, from what I could tell, the package source that created the build for the 0.6.4 release. However, when this changes in future, so too would the
PKGBUILD file have to be modified and re-uploaded to the AUR.
A solution to this manual editing it to use tags, as I think you have alluded to. I expect by using the tags suggested (stable, development, nightly as appropriate) the user would have the option of using the one they choose as a direct download and compile on their box. The user would rebuild each time there is a release directly from Github.
From what I can determine from your tag list there is no tag with stable, development, etc. that can be used yet. Is this difficult to add?
So far as platforms go, if the source can be compiled on various archictures, then the
PKGBUILD can just needs to specify what they are (e.g., arch=(‘i686’ ‘x86_64’)).
If you think it is better to just distribute the .tar.zst package and build that yourselves for the architectures involved with each release then the
PKGBUILD file can just point to the tar.zst file to download from the kopia github repo using a tag to find it. Either way is possible. It is just that with the tar.zst package file the
PKGBUILD file would also have to be modified to reflect the new version as the filenames change along with its checksum (as I understand this process, but I could be corrected)
As Kopia is still under development (?) I would have thought that just providing a mechanism to install the lastest release would be adequate. If a
PKGBUILD was maintained by someone and perhaps included in the kopia github repo then it could be uploaded to the AUR after each release/change (if it in fact changes at all) and that would be sufficent for an Arch user to install it.
I hope I am making some sense in answering your questions, but I might have missed the point completely.
I might have to do some more reading up on the publishing process for the AUR and get back.