| 1 |
This version shows both methods of handling vendor tarballs mentioned on |
| 2 |
the previous thread. |
| 3 |
|
| 4 |
The first method, while it removes the src_prepare function, forces a |
| 5 |
maintainer to re-pack a new vendor tarball for every release. |
| 6 |
|
| 7 |
The second method allows a maintainer to decide when a new vendor |
| 8 |
tarball is needed. |
| 9 |
|
| 10 |
An ebuild using this would look the same as in the previous round, so |
| 11 |
I'm not including any examples. |
| 12 |
|
| 13 |
William Hubbs (1): |
| 14 |
go-module.eclass: introduce new eclass to handle go modules |
| 15 |
|
| 16 |
eclass/go-module.eclass | 100 ++++++++++++++++++++++++++++++++++++++++ |
| 17 |
1 file changed, 100 insertions(+) |
| 18 |
create mode 100644 eclass/go-module.eclass |
| 19 |
|
| 20 |
-- |
| 21 |
2.21.0 |
Archives