Re: [PATCH 6/6] docs: downloads: Point to gitlab for go module sources
On Tue, Mar 14, 2023 at 10:36:58AM +0100, Peter Krempa wrote:
* - Go
- - `libvirt <https://libvirt.org/go/libvirt>`__
+ - `gitlab <https://gitlab.com/libvirt/libvirt-go-module/-/tags>`__
- `gitlab <https://gitlab.com/libvirt/libvirt-go-module>`__
- `issues <https://gitlab.com/libvirt/libvirt-go-module/-/issues>`__
- `github <https://github.com/libvirt/libvirt-go-module>`__
@@ -131,7 +131,7 @@ Integration modules
-
* - Go XML
- - `libvirt <https://libvirt.org/go/libvirtxml>`__
+ - `gitlab <https://gitlab.com/libvirt/libvirt-go-xml-module/-/tags>`__
- `gitlab <https://gitlab.com/libvirt/libvirt-go-xml-module>`__
- `issues <https://gitlab.com/libvirt/libvirt-go-xml-module/-/issues>`__
- `github <https://github.com/libvirt/libvirt-go-xml-module>`__
For these two, I think linking to
https://pkg.go.dev/libvirt.org/go/libvirt
https://pkg.go.dev/libvirt.org/go/libvirtxml
similarly to how we point to the language-specific package repository
for Python, Perl and Rust might make more sense.
On the other hand, in the case of Go we don't explicitly publish
releases to a different system, they get picked up automatically from
the git tags...
Dan?
--
Andrea Bolognani / Red Hat / Virtualization