golang February 2020

golang@lists.fedoraproject.org

4 participants
12 discussions

[go-rpm-macros] Issue #2: EPEL availability
by Nicolas Mailhot 29 Mar '24

29 Mar '24

nim reported a new issue against the project: `go-rpm-macros` that you are following: `` The macro code needs massaging to also work on EPEL. Most of the work is spec side since some of the macros are going to collide with the ones provided by previous iterations of Go macro packages `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/2

2 4

[go-rpm-macros] Issue #3: %goprep should apply patches automatically
by Nicolas Mailhot 29 Mar '24

29 Mar '24

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

6 9

[go-rpm-macros] PR #20: Use --with-tests when running checks also.
by Elliott Sales de Andrade 05 Sep '21

05 Sep '21

qulogic opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Use --with-tests when running checks also. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/20

1 2

[go-rpm-macros] Issue #19: LDFlags Macro Typos
by Brian Exelbierd (bex) 20 Apr '21

20 Apr '21

bex reported a new issue against the project: `go-rpm-macros` that you are following: `` While working with a new package, I needed some LDFlags passed. I am using this construction in my spec: ``` %build LDFLAGS="-X foo=bar " %gobuild ... ``` I have to put the space in quotes at the end as we appear to have space expansion errors. I was talking to @ignatenkobrain and he pointed out: * https://pagure.io/go-rpm-macros/blob/master/f/rpm/macros.d/macros.go-rpm#_3… there is a missing space * https://pagure.io/go-rpm-macros/blob/master/f/rpm/macros.d/macros.go-compil… ${LDFLAGS:-%{?currentgoldflags}} ← should be like that `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/19

3 4

[go-rpm-macros] PR #21: Expose Go build flags directly to spec files as a macro
by Daniel P. Berrange 21 Oct '20

21 Oct '20

berrange opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Expose Go build flags directly to spec files as a macro `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/21

5 10

Google Go fonts
by Nicolas Mailhot 22 Feb '20

22 Feb '20

Hi, The Go font families (Go, Go Mono and Go Smallcaps) are now available in Fedora 32 and 33 as normal system fonts. You’ve all encountered them on godoc.org when reading Go source code examples. Regards, -- Nicolas Mailhot

1 0

Re: Include non-RPM content in buildroot
by Nicolas Mailhot 21 Feb '20

21 Feb '20

Le vendredi 21 février 2020 à 15:57 +0100, Martin Sehnoutka a écrit : > Hi, Hi, > Go went even further in this case and it is > common > to bundle all the dependencies as a source code directly in the > upstream > repository. See this repo as an example: > https://github.com/containers/libpod/tree/master/vendor Since you take Go in example – vendoring (bundling) proved such a maintenance headache upstream that Google had to create a complete new packaging system to get rid of it. Not for Fedora or Linux people, but because they had huge problems with unmaintained, holed and non-legal code lurking in this kind of vendor pile. So Go (upstream) is going away from the kind of practice you’re advocating. And Google’s implementation of versionning in Go modules is even stricter and more rigid than the one in rpm (precisely because they tried the lala-lala let’s bundle everything without caring about versions, and were badly burned). From a technical POW, we need to improve the mapping of their packaging system and then integrating the Go ecosystem in Fedora will be no harder than integrating any other language component (easier, because the language-specific package manager produces very regular sources). From a maintenance POW dumping huge piles of unmanaged third-party code on build farms just does not work long term. That’s why Google had to break its vendor piles in atomic Go modules. From a process POW, Fedora is not ready. Not because out tech does not work but because our processes can not handle the pile of atomic components generated by upstream practices. Since the problem is process, not technical side, please work on the process side, instead of trying to bypass the process with bad technical solutions. Regards, -- Nicolas Mailhot

1 0

[Fedocal] Reminder meeting : Go SIG Meeting
by jcajka＠fedoraproject.org 16 Feb '20

16 Feb '20

Dear all, You are kindly invited to the meeting: Go SIG Meeting on 2020-02-18 from 16:00:00 to 17:00:00 UTC At fedora-golang(a)irc.freenode.net The meeting will be about: Meeting of Go SIG. For proposed agenda see the tagged tickets https://pagure.io/GoSIG/go-sig/issues?status=Open&tags=meeting Source: https://apps.fedoraproject.org/calendar/meeting/9344/

1 0

Go SIG meeting 4.2.2020(tomorrow)
by Jakub Cajka 04 Feb '20

04 Feb '20

Hello, sorry for short notice. I will not be able to chair tomorrow Go sig meeting as I will be traveling. Neal, Nicolas could please chair it? Thank you, JC

2 1

[golist] PR #27: Fix not listing packages with external tests only
by Ondřej Budai 03 Feb '20

03 Feb '20

obudai opened a new pull-request against the project: `golist` that you are following: `` Fix not listing packages with external tests only `` To reply, visit the link below or just reply to this email https://pagure.io/golist/pull-request/27

4 15

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang February 2020