On 2018-02-12, Boris Manojlovic
Looking at issue regarding "vendorization" of acmetool, it was already asked on issue tracker https://github.com/hlandau/acme/issues/132 and as can be seen official comment regarding it is that it will never be done as commit into repository, so my only option is to provide binary myself, but doing that in my view is not something that is easily repeatable - what i wanted to do exactly with using specific packages, again if that is policy i will try to do that instead even if i do not like it too much.
Alright, I'm a little confused about the conclusion of that issue. As you've probably noticed, openSUSE doesn't use Debian's Go packaging system (for the primary reason of "we tried it with Ruby and it turned out to be a nightmare"). So from that perspective, the issue you linked shouldn't affect packaging in openSUSE. Maybe I missed something, but I didn't see a comment saying "we will never commit vendor/ into our tree". At the same time, it does look like that repo doesn't actually vendor their sources (and it does contain third-party repositories like "github.com/hlandau/goutils" as well as some packages from "golang.org/x/..."). Builds in OBS don't have access to the internet, and in addition builds in OBS should be reproducible. So from my perspective, the current status of the upstream project is that they should vendor their packages (using the standard Go 1.5+ vendoring style). (As an aside, I have been planning some work on improving the state of packaging vendor/-style packages in different languages. So even if they choose to just provide a "vendor.conf" or similar manifest, I can help you with automated pulling and packaging of those components.) -- Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/