git commit to link with pkgver()

Joel · 2017-12-02 00:12:57

I'd like to make an arch package one of my software hosted on github, I'd like to take advantage of pkgver() function to match the one "commited" on github, but I don't know how to do it, I understand how to declare it in PKGBUILD, but not in my commited git.

Any help, please?

progandy · 2017-12-02 00:27:27

If you wish to create a release with a version number in git, I suggest you create a tag:
https://git-scm.com/book/en/v2/Git-Basics-Tagging
In order to create a standard PKGBUILD, you can then set the pkgver manually and download the archive for that tag.
For a VCS package, the pkgver function can display the tag version and count the commits since that tag.

For github, you can use the "release" function with is built on top of tags
https://help.github.com/articles/about-releases/
https://help.github.com/articles/creating-releases/

Last edited by progandy (2017-12-02 00:29:30)

jasonwryan · 2017-12-02 00:34:17

Moving to Creating Packages...

Xyne · 2017-12-02 00:39:14

I am not sure that I understand your question. What do you mean by "match" here?

Joel wrote:

take advantage of pkgver() function to match the one "commited" on github

Normally the head of the master branch will be used to build the package. Every time the package is built, makepkg will fetch the last commit (and update the package version in the pkgbuild). If you want to use something else, you can configure the PKGBUILD to check out specific tag or commits or even other branches (read the VCS section of thethe PKGBUILD man page for details). No changes are needed in the git repo. Everything is configured in the PKGBUILD.

You can tag your commits in the git repo and use a version of pkgver() to include them in the package version but that is not necessary. The wiki page that you linked contains examples of pkgver() functions that will create unique incremental versions by counting commits without using tags.

If this doesn't answer your question, can you give an example of what you are trying to do?

edit
Just to clarify, there are two types of "git" packages.

Packages that follow the HEAD of a branch. These packages include the "-git" suffix. The PKGBUILD will automatically fetch the last commit on the target branch and build it without any intervention.
Stable packages that check out fixed commits from a git repo. These do not use the "-git" suffix. The PKGBUILD will fetch and build a specific version of the package. For example, if you have stable tagged releases (e.g. v3.3) then you could write a PKGBUILD that checks out the tag "v3.3". When a new version is release (e.g. v3.4), the PKGBUILD would need to be updated to checkout the tag "v3.4". Instead of tags, you could use commit hashes to designate specific commits. This can be done using URL fragments as explained in the PKGBUILD man page.

Last edited by Xyne (2017-12-02 00:47:16)

Joel · 2017-12-02 01:03:01

Right now, I'm not in my home town but as soon as possible I will try what @progandy seems to pointed me to the right direction.

Arch Linux

#1 2017-12-02 00:12:57

git commit to link with pkgver()

#2 2017-12-02 00:27:27

Re: git commit to link with pkgver()

#3 2017-12-02 00:34:17

Re: git commit to link with pkgver()

#4 2017-12-02 00:39:14

Re: git commit to link with pkgver()

#5 2017-12-02 01:03:01

Re: git commit to link with pkgver()

Board footer