Closed williamjameshandley closed 4 years ago
This release contains only plugin changes not binary(the binaries are still 2.8.1) Are you having problems with this release?
Only in that it messes up the aur build system, and if you're going to have a patch version number in the directory hierarchy, it should be consistent with the release number.
Hey @williamjameshandley, thanks for drawing our attention. can you please elaborate, how did this messed up? from what I see it pulls the whole extension from '$ {url} / archive / $ {pkgver} .tar.gz' which will pull the extension with its relevant binaries (as soon as pkgver is updated to 2.8.2)
@williamjameshandley - I found it,
cp -r binaries/${pkgver}/x86_64-unknown-linux-musl/ $installpath/binaries/${pkgver}
we are managing two separate release cycles for the plugin and for the binary.
the binary version is determined by the .gitignore !binaries/version field
can your PKGBUILD be modified to pull the relevant binary version from .gitignore !binaries?
Ah, I see! one moment...
Great, that's pushed. Many thanks for your explanation and help @dimacodota
sure, no problem,
BTW, i would suggest to always pull the latest plugin version
by calling https://github.com/codota/tabnine-vim/releases/latest
In release 2.8.2, the binaries are still stored in binaries/2.8.1