golang September 2020

golang@lists.fedoraproject.org

8 participants
14 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] PR #23: macros: Accept options for %gotest
by Alexander Todorov 21 Jun '21

21 Jun '21

atodorov opened a new pull-request against the project: `go-rpm-macros` that you are following: `` macros: Accept options for %gotest `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/23

4 7

[go-rpm-macros] Issue #25: Consider using -trimpath
by Debarshi Ray 26 Apr '21

26 Apr '21

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`. Apparently Arch Linux already uses it. `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/issue/25

4 9

[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 #26: Remove tildes from goname
by Benjamin Lowry 20 Apr '21

20 Apr '21

blowry opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Remove tildes from goname `` To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/26

6 13

[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

Help reqest: dependencies for packaging writefreely
by Edd Salkield 27 Sep '20

27 Sep '20

Hi all, I'm currently working on packaging github.com/writeas/writefreely, a platform for building writing spaces. Some of its dependencies are currently not packaged for Fedora, so I'm seeking some advice on the granularity to which I should be packaging each dependency. I initially wrote this email to packaging(a)lists.fedoraproject.org, and I got directed here, so apologies if you're in both lists. github.com/writeas/writefreely depends on github.com/writeas/web-core. This is a library that is used by the project developers (write.as) for all their shared code. It is likely that this will be used as a dependency for future packages (for example, when their photo sharing service, snap.as, gets released), but unlikely that it will ever be used by anyone other than these developers. Therefore, should github.com/writeas/web-core be its own package, should I bundle it in with writefreely, should it be a subpackage of writefreely, or indeed something else? Additionally, web-core has its own dependencies of the same kind. Where possible, I have submitted PRs[1,2,3] to their repo to reduce unnecessary dependencies, but web-core still depends upon github.com/writeas/impart and github.com/writeas/openssl-go. These libraries are both unlikely to be used anywhere else; should these be bundled too? If the correct course of action is to bundle the dependencies (in a nested way), I would really appreciate somebody experienced at packaging Go packages to give some guidance on how to do this sensibly with the Go SPEC file macro system. This is especially since the current documentation[4] seems pretty light on the topic of dealing with SPEC files with multiple sources. Also, this is my first time joining a mailing list to actually get involved with the Fedora project, so do let me know if this sort of question actually belongs elsewhere. Kind regards, Edd Salkield [1] https://github.com/writeas/web-core/pull/6 [2] https://github.com/writeas/web-core/pull/8 [3] https://github.com/writeas/web-core/pull/10 [4] https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/

2 2

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

26 Sep '20

Dear all, You are kindly invited to the meeting: Go SIG Meeting on 2020-09-28 from 19:00:00 to 20:00:00 Europe/Prague 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/9758/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang September 2020