On 2018-02-09, Boris Manojlovic
as i have done preliminary work on packaging letsencrypt tool called acmetool, i would like to ask what would be best course of action to push packages to devel:language:go and after that into factory as is. Everything boils down to one question: Should i vendor in everything so i can "just" build binary or repackage binary (was doing that too for my own purpose until i built all dependencies by hand :) )?
The key thing to note is that we do not package Go libraries anymore -- please vendor all your dependencies (upstream should already be doing this) and then just publish a package for the *binary*. There are plenty of examples in devel:languages:go and Virtualization:containers of how you can package a Go binary using golang-packaging -- just make sure that you BuildRequires: golang(API) = VERSION. However, you really shouldn't submit a binary to devel:languages:go just because it's written in Go (there are some, but IMO those are mostly mistakes and shouldn't be copied). Since it's a LetsEncrypt tool you might want to put somewhere in the server:* namespace. golang-packaging is already in openSUSE, so you can use it outside of devel:languages:go. -- Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/