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 the logic. On Mon, Jul 9, 2018 at 12:15 PM, Paride Legovini <p...@ninthfloor.org> wrote: > Package: dh-golang > Version: 1.34 > Severity: normal > > Hi, > > 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: > > https://github.com/golang/go/issues/24253 > > 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: > > https://salsa.debian.org/go-team/packages/fscrypt/blob/ > d15d123eb301d50c0376a10615e472054dd3b88d/debian/rules#L36 > > Paride > _______________________________________________ > Pkg-go-maintainers mailing list > Pkg-go-maintainers@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/ > pkg-go-maintainers -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers