packaging gnvim about gnvim HOT 5 CLOSED

Currently the version number to the final build is extracted from git tags. How would that work with shallow clones? With --always flag and shallow clone, the version number would end up being a git hash, which in it self isn't really describable. Can you do a shallow clone so that it fetches the latest tag too?

from gnvim.

Having a git hash is better than lying about the version ? It means it's a dev version. Sounds good to me else how am i supposed to build the dev version ? Btw if the version number should remain static, better write it into the file than using git. Tarballs typically dont contain the .git folder and i myself had to go to extra length to fetch bot the git folder and the tags (not fetchef by default). Otherwise i may patch the build.rs to bypass the git logic.

from gnvim.

This script might be helpful: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gnvim-git

from gnvim.

thanks why are there 2 pkgver ? with nix, I think the rust building process will fail if I use the plain make (no internet access during builds) so I have to follow the standard way. It is just a matter of setting a version that upstream an packagers are happy about.

from gnvim.

Arch allows for package versions with rel versions, e.g. 0.1.0-a1a1a where a1a1a is the HEAD sha.

If you can't have internet access during installation perhaps you'll have to distribute the binary directly, i.e. building during packaging and just copying the binary on package install.

from gnvim.