[pkg-go] Bug#903385: Bug#903385: dh-golang: Allow the "build" dh stage to call "go build" instead of "go install"
stapelberg at debian.org
Mon Jul 9 11:40:51 BST 2018
Would such a flag be useful for any other package than the fscrypt package?
If no, I’d recommend to not change dh-golang for the time being, and let
this be a one-off in the fscrypt package until it makes sense to centralize
On Mon, Jul 9, 2018 at 12:15 PM, Paride Legovini <pl at ninthfloor.org> wrote:
> Package: dh-golang
> Version: 1.34
> Severity: normal
> There is at least one case when it would be preferable to have the build
> dh stage to call ’go build’ instead of ’go install’. This is when
> building c-shared libraries with -buildmode=c-shared. In this case ‘go
> install’ builds the shared library object, but gives it a ‘.a’ extension
> and installs it in a not well defined location. This is discussed in this
> upstream issue:
> The upstream indication is that "The expectation is that people will use
> go build -buildmode=c-shared -o foo.so" and that using ‘go install’ "will
> put the shared library in a relatively unpredictable place".
> Given these facts, I think dh-golang should support a ‘go build’ mode.
> One way this could be implemented is via a --build-only flag to be
> passed to dh_auto_build. If there is consensus on this I can send a
> patch implementing it.
> This problem arose while packaging fscrypt, see in particular:
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at alioth-lists.debian.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-go-maintainers