Tong, > On Nov 24, 2018, at 10:15 PM, Tong Sun <[email protected]> wrote: > > This is a question for my > Bug#901583: ITP: golang-github-danverbraganza-varcaser > 901583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901583 > > Should I do it or not?
Based on my understanding of your ITP you want to package golang-github-danverbraganza-varcaser in order to later package github.com/go-easygen/easygen, you should in fact continue packaging it. > I.e., seem to me that all libraries written in Go and for Go are > better be packaged in order to avoid problems like above. However, on > https://go-team.pages.debian.net/packaging.html > <https://go-team.pages.debian.net/packaging.html> As you noted all dependencies for go packages need to be packaged separately. > I also read, > >> Libraries written in Go are packaged for Debian with the only purpose of >> building other Go programs for Debian. They are specifically not available >> for users in their regular development workflow. For that, users should use >> go get. > > Is my understanding correct that the above is saying that, all > libraries written in Go and for Go should not be packaged, but user > should use go get instead? The passage you quoted talks about libraries that are used when users do local go development. It does not apply to packages users are packaging for Debian. Does that make sense? Stephen
