Robin Candau pushed to branch main at Arch Linux / Packaging / Packages / ansible-language-server
Commits: 4af0f1f2 by Robin Candau at 2024-07-22T11:35:44+02:00 Add README with explanations about versioning and instructions about updating the package - - - - - 1 changed file: - + README.md Changes: ===================================== README.md ===================================== @@ -0,0 +1,12 @@ +# ansible-language-server + +## Versioning and updating the package + +The Ansible language server used to have its [own repository](https://github.com/ansible/ansible-language-server) but, at some point, upstream dediced to archive it and merge it into their [vscode plugin repository](https://github.com/ansible/vscode-ansible/issues/1134). + +The ansible-language-server specific files are still accessible in a [separate directory](https://github.com/ansible/vscode-ansible/tree/main/packages/ansible-language-server) in the vscode-ansible repo but upstream did not implement a separate tagging for it, making the packaging of the language server itself (meaning not including the whole vscode plugin) more difficult. +A [request has been made](https://github.com/ansible/vscode-ansible/discussions/1243) to upstream in order to impletement a separate versioning for ansible-language-server, however we have no ETA as of now (neither an actual confirmation that this will happen at some point). + +In the mean time, we got the [nvchecker integration](https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/blob/main/.nvchecker.toml?ref_type=heads) looking for ansible-language-server new releases via the [npm registry](https://www.npmjs.com/package/@ansible/ansible-language-server) (which has specific releases/versioning for it). The lack of tagging on the source repo side forces us to use a `_commit` mechanism in the PKGBUILD to point to the commit that bumped the version of ansible-language-server in the associated [package.json file](https://github.com/ansible/vscode-ansible/blob/main/packages/ansible-language-server/package.json) matching the version from the npm registry (you can use `View git blame` on the "version" line of the package.json file to see which upstream commit bumped it). + +Unfortunately, the lack of tagging in the upstream repo for the Ansible language server itself also prevents us to add the usual `pkgver()` verification mechanism (e.g. verify that `$_commit` indeed points to the commit used for the tag that matches `$pkgver`) but, in the current state of things, this is probably the best we can come up with. View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/commit/4af0f1f2badc56257de7cd7a1d48bd3ea5a377d5 -- View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/commit/4af0f1f2badc56257de7cd7a1d48bd3ea5a377d5 You're receiving this email because of your account on gitlab.archlinux.org.
