On 20/02/18 12:20, Michael Stapelberg wrote: > I’m only aware of one package (jacobsa/crypto) which has a > Debian-specific patch that requires the use of an architecture-specific > build tag. My proposed solution for this is to either specify the > architectures (as opposed to custom pointer size build tags) in the > files (they change rarely enough), or at least add the amd64 architecture. > > Are you aware of other packages which use the same technique? If so, it > might be good to write up a little bit of documentation, and perhaps > even make this a feature of dh-golang.
the ones I have in mind would work for amd64 without the tags. Others could be patched. The one that is not going to be easy without a lot of medding is x/sys. > This particular example is moot since dh-golang 1.31’s > install-testdata-by-default change :). Cool > I understand your concern. I suggest we try my suggested approach and > re-evaluate at some point down the road (a quarter? a year?) whether > keeping it up is feasible and worthwhile. We can always course-correct, > there’s no lock-in here. Sounds good to me. -- Martín Ferrari (Tincho) _______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
