This version shows both methods of handling vendor tarballs mentioned on the previous thread.
The first method, while it removes the src_prepare function, forces a maintainer to re-pack a new vendor tarball for every release. The second method allows a maintainer to decide when a new vendor tarball is needed. An ebuild using this would look the same as in the previous round, so I'm not including any examples. William Hubbs (1): go-module.eclass: introduce new eclass to handle go modules eclass/go-module.eclass | 100 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 eclass/go-module.eclass -- 2.21.0
