If you are building a package that tracks the master branch of git, you want to build the latest version of it.
You could also track various branches or tags in the package as well. In each case, the assumption is that you would want to build the latest commit in that branch. This is mostly useful for developers testing their software or the latest feature. On my packages in aur I will bump the version if I am tracking a new stable branch, or a particular feature has been implemented and proven to be stable. On Tue, Dec 6, 2022, 14:42 Doug Newgard <[email protected]> wrote: > On Tue, 6 Dec 2022 13:34:05 +0000 > Polarian <[email protected]> wrote: > > > Hello, > > > > I am pretty new to the AUR, however I have read through the arch wiki > > and this question is not really referenced there. > > > > I have seen some -git packages which update the package on each new > > commit to master, which is what I thought -git packages should aim to > > do, however I have seen others which only do it for every 5 or so > > commits to save time. > > > > However I have also seen another method, of just not bumping the package > > version and have the package clone master and then append the latest git > > commit to the package name when building it. > > This is how -git packages work. If it doesn't do this but uses a pinned > commit > instead, it's not a -git package. > > The version displayed in the AUR doesn't matter. The people bumping the > pkgver > every commit or every 5 commits or whatever are just wasting their time, > and > annoying their users. > > > What is the actual conventional method of producing a -git package for a > > piece of software? > > > > Thank you, > > Polarian > >
