| 1 |
All, |
| 2 |
|
| 3 |
after some further discussion, I decided to split the eclass. |
| 4 |
The go-module eclass in this thread would be used if your upstream |
| 5 |
project vendors its dependencies and the go-module-vendor eclass would |
| 6 |
be used otherwise. |
| 7 |
|
| 8 |
Thanks, |
| 9 |
|
| 10 |
William |
| 11 |
|
| 12 |
William Hubbs (2): |
| 13 |
go-module.eclass: new eclass for go modules |
| 14 |
go-module-vendor.eclass: new eclass for go modules that do not vendor |
| 15 |
|
| 16 |
eclass/go-module-vendor.eclass | 133 +++++++++++++++++++++++++++++++++ |
| 17 |
eclass/go-module.eclass | 79 ++++++++++++++++++++ |
| 18 |
2 files changed, 212 insertions(+) |
| 19 |
create mode 100644 eclass/go-module-vendor.eclass |
| 20 |
create mode 100644 eclass/go-module.eclass |
| 21 |
|
| 22 |
-- |
| 23 |
2.21.0 |
Archives