[go-rpm-macros] PR #21: Expose Go build flags directly to spec files as a macro

rishi commented on the pull-request: `Expose Go build flags directly to spec files as a macro` that you are following: `` Could we please have a new `go-rpm-macros` build in Fedora that includes `%gobuildflags` (with the corresponding RPM spec changes discussed here)? We have Go code in [toolbo

[go-rpm-macros] Issue #25: Consider using -trimpath

rishi reported a new issue against the project: `go-rpm-macros` that you are following: `` See [this](https://github.com/containers/toolbox/pull/448) [Toolbox](https://github.com/containers/toolbox) discussion for context. It might be good to include `-trimpath` in `%gobuild` and `%gobuildflags

[go-rpm-macros] PR #21: Expose Go build flags directly to spec files as a macro

rishi commented on the pull-request: `Expose Go build flags directly to spec files as a macro` that you are following: `` Ping `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/21 ___ golang mail

[go-rpm-macros] PR #21: Expose Go build flags directly to spec files as a macro

rishi commented on the pull-request: `Expose Go build flags directly to spec files as a macro` that you are following: `` Yay! We have 3.0.9 now. Thank you. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/21 _

[go-rpm-macros] Issue #25: Consider using -trimpath

rishi added a new comment to an issue you are following: `` Ping `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/25 ___ golang mailing list -- golang@lists.fedoraproject.org To unsubscribe send an emai

[go-rpm-macros] PR #21: Expose Go build flags directly to spec files as a macro

rishi commented on the pull-request: `Expose Go build flags directly to spec files as a macro` that you are following: `` The RPM spec file changes slipped through the cracks. I filed: https://src.fedoraproject.org/rpms/go-rpm-macros/pull-request/1 `` To reply, visit the link below or just reply

[go-rpm-macros] Issue #25: Consider using -trimpath

rishi added a new comment to an issue you are following: `` I agree that `-trimpath` doesn't make any difference for official Fedora packages. Although, I wonder if it might help with ad-hoc local uses of `rpmbuild`. I filed this issue in the context of [this](https://github.com/containers/too

[go-rpm-macros] PR #34: Add BUILDTAGS to %gobuildflags

rishi commented on the pull-request: `Add BUILDTAGS to %gobuildflags` that you are following: `` > I'm actually confused why %gobuildflags exists, because > %gobuild below that doesn't use it. In fact, %gobuild > uses an exact copy of gobuildflags with BUILDTAGS > already there. A bit of Git for

[go-rpm-macros] PR #34: Add BUILDTAGS to %gobuildflags

rishi commented on the pull-request: `Add BUILDTAGS to %gobuildflags` that you are following: `` Speaking as someone who maintains a code base where `go build` is invoked by Meson ... > I traced through the commit history and found the commit[1] > where the %gobuildflags macro was created. It l

[go-rpm-macros] PR #34: Add BUILDTAGS to %gobuildflags

rishi commented on the pull-request: `Add BUILDTAGS to %gobuildflags` that you are following: `` Since commit [c593262127afd28d](https://pagure.io/go-rpm-macros/c/c593262127afd28d9f0b52a78a3cf0ef5b14673f) or PR [#35](https://pagure.io/go-rpm-macros/pull-request/35), `%gobuild` does use `%gobui

[go-rpm-macros] PR #34: Add BUILDTAGS to %gobuildflags

rishi commented on the pull-request: `Add BUILDTAGS to %gobuildflags` that you are following: `` Anyway, I think this pull request should be closed because `BUILDTAGS` is already part of `%gobuildflags` these days. See commit [c593262127afd28d](https://pagure.io/go-rpm-macros/c/c593262127afd28

[go-rpm-macros] PR #71: Revert "Set _dwz_low_mem_die_limit only when a go binary is built"

rishi opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Revert "Set _dwz_low_mem_die_limit only when a go binary is built" `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/71 -- ___

[go-rpm-macros] PR #71: Revert "Set _dwz_low_mem_die_limit only when a go binary is built"

rishi commented on the pull-request: `Revert "Set _dwz_low_mem_die_limit only when a go binary is built"` that you are following: `` ping `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/71 --

[go-rpm-macros] PR #71: Revert "Set _dwz_low_mem_die_limit only when a go binary is built"

rishi commented on the pull-request: `Revert "Set _dwz_low_mem_die_limit only when a go binary is built"` that you are following: `` ping `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/71 --

[go-rpm-macros] PR #71: Revert "Set _dwz_low_mem_die_limit only when a go binary is built"

rishi commented on the pull-request: `Revert "Set _dwz_low_mem_die_limit only when a go binary is built"` that you are following: `` Thanks, @gotmax23 ! `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/71 -- _