9
[Linux, AUR] Creating initial PKGBUILD script for -git package, what pkgver do I put in? (lemmy.ml)
submitted 1 month ago by to c/programming@programming.dev
8 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.ml/post/53225512

I want to create and upload an AUR package. For context, I did that years ago for specific releases, but now I want to create a new package that focuses on upstream Git without specific releases.

What do I write to the pkgver= value? Do I just take the latest version there? Because it is downloading with git clone the version number will not change and the PKGBUILD script will compare pkgver() instead. So what is the purpose of pkgver= for when downloading and building from Git directly? Looking at examples from other existing packages, they all have a number there. But its mostly outdated, so I don't get it.

pkgname=thename-git
_pkgname="$(pkgname%-git}"
pkgver=???

pkgver() {
    cd "${_pkgname}"
    git describe --long | sed 's/\([^-]*-g\)/r\1/'
}

I am reading and researching, but need some assistance for this question. Currently reading the Archwiki:

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 1 month ago

The thing is, when installing a -git package, then the function pkgver() is used to extract a version number to compare if its newer than what you have installed. And this is normally as you saw semver+githash. My question is, what do I write to pkgver= variable, that seemingly get ignored. But for whatever reason there is a version number listed on all -git packages. I'm just confused what I have to write there in an initial upload. It's important to distinguish between the variable and the function. This is a specific AUR thing and I could not get the information from the documentation.

  • permalink
  • fedilink
  • source
  • parent