Hi,
This is not very important now and it’s an easy change at any stage. I think
the Go library import paths for packages are something that need consideration.
I’m currently using my GitHub in the import paths to keep things easily “go
get”-able.
This results in imports like:
import “github.com/vladvelici/spdx-go/spdx”
I have tried to use something like “git.spdx.org/spdx-tools-go/spdx” and
“git.spdx.org/spdx-tools-go.git/spdx” but the go get tool tries to clone:
git clone [ git:// | https:// | http:// ]git.spdx.org/spdx-tools-go
(no .git at the end)
So, naturally, doubling the .git in the import path quite did it:
import “git.spdx.org/spdx-tools-go.git.git/spdx”
Although it works, it’s terribly ugly.
Would it be possible to either:
1. Make the repository clone-able at git.spdx.org/spdx-tools-go (without the
.git). This will result in import paths like
“git.spdx.org/spdx-tools-go.git/spdx”.
2. Add the meta tag <meta name="go-import" content=“spdx.org git
http://git.spdx.org/spdx-tools-go.git”> to spdx.org, spdx.org/spdx,
spdx.org/tag and spdx.org/rdf. See more in Go documentation [1]. This would be
preferred, I think, as it will result in shorter import paths: “spdx.org/spdx”
Thanks,
Vlad
[1]: http://golang.org/cmd/go/#hdr-Remote_import_paths
_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech
