Perhaps others might find this useful too.

I'd like to give back a little to the arch community by sharing my mkpkg tool available on aur [1] and source is housed on github [2] where there is a detailed readme file.

This tool helps to automate rebuilds when they're needed for reasons other than the package itself has updated.

Rebuild triggers are defined as a list in the PKGBUILD. When a trigger is tripped then a rebuild is done. This helps when the actual package is unchanged but something the package uses changes in a way that makes a rebuild desirable or necessary:

There are 3 kinds of triggers: 1 for files and 2 for packages.

 - a package has been installed since the last build
 - a package version has passed a specific threshold
 - a file is newer than the last build

Some examples of build triggers.

 - 'python>minor' -> rebuild if major.minor vers > than at last build
 - 'xxx.service'  -> rebuild if file has been updated since last build
 - 'gcc>major'    -> rebuild if gcc major version newer than last build
 - 'some-lib'     -> rebuild if more recent than last build
 - 'foo>last'     -> rebuild if version greater than at last build
 - 'foo>=3.10'    -> rebuild if version is >= 3.10

regards

gene

[1] https://aur.archlinux.org/packages/mkpkg
[2] https://github.com/gene-git/Arch-mkpkg

Reply via email to