eclasses in this overlay vs those in the portage tree

[simonvanderveldt]

Hi Mauro,

This is more of a question than an issue, hope that's OK :)

I was wondering what your view on the eclasses in the portage tree (https://github.com/gentoo/gentoo/blob/master/eclass/golang-base.eclass, https://github.com/gentoo/gentoo/blob/master/eclass/golang-build.eclass, https://github.com/gentoo/gentoo/blob/master/eclass/golang-vcs.eclass and https://github.com/gentoo/gentoo/blob/master/eclass/golang-vcs-snapshot.eclass) is and what the differences are between the eclasses in this overlay vs the eclasses in the portage tree.

I'm asking this because I'm having issues with making an ebuild for a simple golang application (https://github.com/99designs/aws-vault/) in that golang-base from the gentoo tree is hardcoded to do doins for the pkg and src directories (https://github.com/gentoo/gentoo/blob/master/eclass/golang-base.eclass#L79), this fails when using go 1.10+ since there is only a bin directory and no longer a pkg directory (the go package cache now resides in GOCACHE if I understand it correctly looking at the release notes https://tip.golang.org/doc/go1.10#build).