Robin Candau pushed to branch main at Arch Linux / Packaging / Packages / ansible-language-server
Commits: e0566e63 by Robin Candau at 2024-07-22T11:39:34+02:00 Update README - - - - - 1 changed file: - README.md Changes: ===================================== README.md ===================================== @@ -7,6 +7,6 @@ The Ansible language server used to have its [own repository](https://github.com 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). +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 in GitHub 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/e0566e63bd7c940753734696affdc2d0f9e70057 -- View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-language-server/-/commit/e0566e63bd7c940753734696affdc2d0f9e70057 You're receiving this email because of your account on gitlab.archlinux.org.
