November 2018 - openSUSE Go - openSUSE Mailing Lists

[opensuse-go] Go Modules
by Aleksa Sarai 09 Nov '18

09 Nov '18

Hi all, We are going to be facing quite a few issues in the near future because of Go modules. Go 1.11 added this concept of modules, which is supposed to eventually replace vendor/ and all of the other awful systems Go developers have had to deal with for the many years. Unfortunately, they are far from ideal at the moment. The current design of Go modules effectively requires that you download all of your dependencies from the internet during "go build". "go mod vendor" will generate a backwards-compatible vendor/ for you, *but* in order to stop "go build" from downloading stuff from the internet (which is disallowed in OBS obviously) you need to pass "-mod=vendor". The kicker is that only Go 1.11 supports "-mod=vendor", while "go build" supports Go modules as far back as Go 1.9. So when building currently we have to delete go.mod and go.sum. I proposed about a year ago that we should have some OBS service to deal with the vendoring problem by automating the pulling and setting up of vendor directories. Personally I think it's about time I dust off that idea and actually get to work on it -- since we now are going to need it for Go since (as I've discovered) some projects don't commit a vendor/ anymore. -- Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH <https://www.cyphar.com/>

3 4

[opensuse-go] Stripping of Go binaries
by Matthias Bach 09 Nov '18

09 Nov '18

Hi! The Packaging Go page in the Wiki [1] recommends to use the %{go_nostrip} macro to prevent issues with Go tooling. However, it is unclear to me whether this recommendation should also be followed for application binaries. After all, the page mostly focuses on the, now deprecated, development packages. For these I fully see the purpose of unstripped binaries. However, for normal applications it seems to me stripping would make sense, as it reduces binary size and it is unlikely people will run tooling on those. So what's the best practice regarding stripping application binaries? Kind Regards, Matthias [1]: https://en.opensuse.org/openSUSE:Packaging_Go -- Dr. Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke

5 10

[opensuse-go] Go ending support for binary-only go (language) packages
by Jeff Kowalczyk 09 Nov '18

09 Nov '18

I wanted to mention this accepted Go proposal here, to understand if anything in the openSUSE/SUSE sphere currently ships binary-only Go packages to be imported by other Go code (not to be confused with operating system packaging of go binaries): go#28152 cmd/go: drop support for binary-only packages https://github.com/golang/go/issues/28152 Recently accepted by upstream, slated for go1.13 (ETA Aug 2019). Thanks, Jeff -- Jeff Kowalczyk Software Engineer, Go Developer Experience SUSE Linux -- To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org

2 1