Hello Nicolas, Also, we have recently discussed this matter with Robert-André Mauchin (@eclipseo).
To make a long story short, for packaging binaries we basically have two options for EPEL8: 1) Using vendored dependencies aka using Go modules functionality, and providing modules archive as a SourceXX. It works, but evidently it produces bulky SRPMS, and requires some efforts to maintain a single spec across various branches as well; 2) Using side-tags (the approach I'm not really familiar with, but it looks promising). Would be glad if someone could provide a working snippet set which could be used for packaging Go binary packages. On Tue, Sep 1, 2020 at 7:17 PM Nicolas Mailhot <nicolas.mail...@laposte.net> wrote: > Le 2020-08-20 22:05, Denis Fateyev a écrit : > > >>> Could anybody provide some more info: are Go rpm macroses not > >> fully backported to RHEL8 currently? Any kind of blockers, perhaps? > > Unfortunately, while the Go-specific logic of the macros is quite > release-agnostic, they depend on some common code in redhat-rpm-config > that did not make it to EL8. The way @rh freezes common tooling at the > start of an EL release inherently conflicts with languages like Go which > are still fast evolving and requiring changes not fossilized a decade > ago. > > And it would be quite hard to both froze initial EL implementation in > stone and provide parallel updates (modularity & containers only work > for leaf features not core shared low level code) > > Regards, > -- > Nicolas Mailhot > -- wbr, Denis.
_______________________________________________ golang mailing list -- golang@lists.fedoraproject.org To unsubscribe send an email to golang-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org
