Golang 1.16
by Robert-André Mauchin
Hello Jakub,
I wanted to ask you at the meeting, how is the update to Golang 1.16
shaping up? Have you tested it on a small batch of packages? Should we
expect breaking changes from upstream again?
Best regards,
Robert-André
2 years, 9 months
Implementing Go modules in F34
by Robert-André Mauchin
Hi,
Following the discussion we had at the meeting, it would be great if we
had the new tooling in F34. As you may know, RHEL9 will be based off
F34; we already missed the mark for RHEL8 which still doesn't support
our current macros, so we have to bundle everything.
I don't expect we will be able to rebuild our 1,600ish packages with Go
modules for F34, so the changes would need to be **fully** backwards
compatible, so we can target F35 without breaking F34.
Nicolas, the issue is mostly in your hands, can we count on you to push
for changes in redhat-rpm-config, package modist and update go-(s)rpm
macros? We would need to move quickly as F34 is approaching. Are your
current work on modules macros backward compatible without any changes
to current packages?
Best regards,
Robert-André
2 years, 9 months
[go-rpm-macros] Issue #28: Allow override of %gomodulesmode
by Jonh Wendell
jwendell reported a new issue against the project: `go-rpm-macros` that you are following:
``
Currently it is hardcoded in macros.go-compilers-golang line 35:
# Turn off Go modules
%gomodulesmode GO111MODULE=off
This is preventing me to build passing the flag "=mod=vendor". I'm currently setting:
%global gocompilerflags "-mod=vendor"
in my .spec.
Build fails with:
build flag -mod=vendor only valid when using modules
Because %gomodulesmode is being passed to go build.
Ideally we should be able to override it, so that it works when trying to use -mod=XXX value.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/28
2 years, 9 months