On Thu, Jun 04, 2015 at 12:27:39PM -0700, Andrew Udvare wrote: > > > On 2015-06-04, at 12:10, William Hubbs <willi...@gentoo.org> wrote: > > > > All, > > > > we are starting to get more go packages in the tree, so we need an > > eclass that properly deals with go live ebuilds. > > Why live only? > > Your eclass does what every other live and non-live ebuild does for Go: > create a temporary Go environment without the package in question. This is > fine (I hate how Go is designed in this respect). I just think non-live Go > packages definitely need an eclass.
The function of this eclass is to take the place of the git-* eclass in the go live ebuilds. You can't rely on git being the vcs upstream uses, and there is no way to tell what the vcs or the vcs URL is reliably from the name of a package, so it is best to use "go get" to grab the source. Please look at "go help importpath" for more details about this. I will start another discussion about non-live ebuilds once this eclass is in the tree, because I do think I see an issue with how they are being done. William
signature.asc
Description: Digital signature
