This is a clone of
https://github.com/gofed/go-macros/issues/56

The problem is actually in golist, not in the macros themselves.
https://pagure.io/golist/issue/2

This issue is about dealing with the consequences of golist behaviour macro-side. If the arch-specific nature of the result can’t be fixed the macros need to move the source code installation point to an arch-specific directory

The arch-specific part is not a huge problem and can be handled (just requires a mass rebuild to move existing packages to an arch-specific root, the mass rebuild works in copr)

However according to @jcajka that also means we only install the files corresponding to other (non arch-specific) build tags, so the resulting source code can not be used to build projects that need another build tag set.