[go-rpm-macros] Issue #3: %goprep should apply patches automatically
by Nicolas Mailhot
nim reported a new issue against the project: `go-rpm-macros` that you are following:
``
`%goprep` should apply patches automatically, so there is no convenience gap with `%autosetup`.
This is generic work that should be done *redhat-rpm-config* side in forge macros and then reused in`%goprep`. Basically:
1. define a `patch_flags<suffix>` rpm variable holding the parameters that should be passed to `%patch<suffix>`
2. define a `default_flags<suffix>` fallback
3. define a `source_patches<suffix>` holding an ordered space separated list of patch suffixes associated with a particular forge/go source.
And then write the usual lua loops to apply it all at the right moment in the spec.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/3
4 weeks, 1 day
Proposal: remove %ix86 from golang_arches for F37
by Robert-André Mauchin
Hi,
So the change deadline is very soon, so I'd like a quick answer on this.
So Fedora is dropping i686 in the near future, only plsnning to support Wine related thingie
as far as I know. Could we too make a move toward this by dropping %ix86 from our supported
arches?
Most Go dev don't bother to do check build on 32 bits platforms and thus we find out many
bugs when building on these arches. arm32 was dropped, now we only have i686 as the
remaining 32 bits arch, removing it would reduce the time spent on bugs and failed builds.
What's your take on it Go Folks? Please answer relaively quickly as we don't have much time
before changes deadline.
Best regards,
Robert-André
1 year, 5 months
packaging: -x and -v make it difficult to diagnose build failures
by W. Michael Petullo
I maintain a number of Go packages for Fedora, including Hugo. I find that
the default use of -x and -v when running "go build" makes it difficult to
diagnose compile problems. A compile error does not necessarily terminate
the Go build process, and with -x and -v the error message is quickly
lost in the volume of output from go build.
I have figured out how to run "go build" in mock without the -x and -v
flags, but I sometimes have to diagnose the build log from the Fedora
build server, and this is very difficult due to the volume of output.
For an example of this, see:
https://kojipkgs.fedoraproject.org//work/tasks/3319/88593319/build.log
I would rather not redefine the default "go build" flags for my
packages. Has there been any thought put into dropping -x and -v?
Does anyone else have trouble with this? Does anyone benefit from the
use of -x and -v? Am I missing an obvious trick?
--
Mike
:wq
1 year, 5 months