nim reported a new issue against the project: `go-rpm-macros` that you are following: `` This is a clone of https://github.com/gofed/go-macros/issues/56
The problem is actually in golist, not in the macros themselves. Sticking it in the macro project for now as they need to be switched to deploy in libdir if this is not fixed
According to @jcajka this needs fixing in any case, because other build options are handled the same way by the Go compiler, so deploying only the files corresponding to a particular set of options means sources can not be used with another one later. And we have some of those in Fedora, for example, optional selinux support in some container projects.
``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/1
The issue: `-devel subpackage is build tag specific` of project: `go-rpm-macros` has been assigned to `nim` by nim.
nim added a new comment to an issue you are following: `` This should be fixed with golist 0.10.0 ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/1
The status of the issue: `-devel subpackage is build tag specific` of project: `go-rpm-macros` has been updated to: Closed by nim.
golang@lists.fedoraproject.org