Currently we have 3 go modules: - github.com/ovirt/go-ovirt https://github.com/oVirt/go-ovirt/ seems that this repo generated by https://github.com/oVirt/ovirt-engine-sdk-go
- github.com/ovirt/go-ovirt-client https://github.com/oVirt/go-ovirt-client - github.com/ovirt/go-ovirt-client-log https://github.com/oVirt/go-ovirt-client-log These modules share the issue of depending on the hosting service and the repo the code is located. I started to work on the imageio go module here: https://gerrit.ovirt.org/c/ovirt-imageio/+/117277 And I'm trying to avoid the issues above by naming the module: ovirt.org/imageio The module name does not depend on the hosting service, or on the actual repo or the location in the repo. To make this work, the web server at ovirt.org should serve this resource: https://ovirt.org/imageio returning an HTML document that contains a magic <meta> tag in the page header <meta name="go-import" content="ovirt.org/imageio git https://github.com/ovirt/ovirt-imageio/imageio-go"/> Is this possible with our current infrastructure? Should we rename all the go modules to fit this scheme? Nir _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EGNSRV4UTIPOJQBDM5MDEENJMKUBVFUD/
