-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packaging gnvim #28
Comments
Currently the version number to the final build is extracted from git tags. How would that work with shallow clones? With |
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. |
This script might be helpful: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gnvim-git |
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. |
Arch allows for package versions with 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. |
I've been trying to package gnvim master but I hit
My package used to work but I think the error is similar to the one in nvie/gitflow#126 , aka git describe fails because I am packaging master's HEAD and not a tag revision. Would it be possible to add the
--always
flag to thegit describe
call in build.rs ?It would make packaging easier.
The text was updated successfully, but these errors were encountered: