Explicitly pass version-string to build, to avoid Git-based misdetection
Not sure if you already have another way of handling this, but current version seems to need this option in order for makepkg to work locally, otherwise it complains about the hardcoded app_version
in build.zig
"disagreeing" (with something which I'm guessing is derived wrongly from the src checkout somehow). Please let me know if this is a stupid misunderstanding, and thanks!
Merge request reports
Activity
added priority3-normal statusunconfirmed labels
- Resolved by Caleb Maclennan
Can you be more specific about what problem this is supposed to solve? I'm able to build from this PKGBUILD both locally on my actual host and in a chroot (the proper way with
pkgctl build
). I don't see any errors or complaints, and the resultingghostty --version
output correctly identifies it's own version. I'm happy to inject a version variable if we need to to get the package properly built, but I'm confused why you even bring this up. Are you actually trying to build a Git HEAD version instead of the exact tagged release in this PKGBUILD?