Libraries written in Go and for Go
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?
On one hand, I see previous messages like this:
https://lists.debian.org/debian-go/2018/09/msg00019.html
- - - - - - - - - - - - - - - - - -
> Is this the right recipe for using gpb buildpackage for a particular
> flavor of ubuntu?
>
> #!/bin/sh
> set -ex
> sudo apt install dh-make-golang
> DIST=bionic git-pbuilder create dh-make-golang github.com/gomatic/renderizer
> dh-make-golang github.com/gomatic/renderizer
Please see the output of this command, it says,
2018/09/08 23:19:29 Build-Dependency "github.com/gomatic/funcmap" is
not yet available in Debian, or has not yet been converted to use
XS-Go-Import-Path in debian/control
- - - - - - - - - - - - - - - - - -
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
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?
I have to admit that I feel the above two information contradict with
each other, and I really don't know whether libraries written in Go
and for Go should not be packaged or not not, including my ITP
Bug#901583.
Can someone explain clearly what should be packaged and what should
use go get please? How clearly to tell them apart, etc.
Thx
Reply to: