On Mon, Aug 24, 2015 at 05:35:39PM -0700, Andrew Udvare wrote: > To correctly support the entire Google API library set, do we need a > separate ebuild for every single one? This definitely can be automated. > > https://godoc.org/google.golang.org/api > > With golang-vcs, using google.golang.org/api for GO_PN is not working > and I think it is because each package must be dealt with separately.
I will take a look at this in more detail, but, yes, from what I see in their README.md, we will need ebuilds for each package. Let me know what you think about how we could automate it. I think we'll have to manually create the ebuilds. William
signature.asc
Description: Digital signature
