On Fri, Jun 12, 2015 at 10:39:57PM +0000, Duncan wrote:
> Patrick McLean posted on Fri, 12 Jun 2015 11:18:29 -0700 as excerpted:
>
> > We could make go ebuilds simply install their sources to something like
> > /usr/share/go/${PN}-${SLOT}.
>
> I'm staying out of the general discussion, but this...
>
> These are sources, please use a location within the PM's sources tree.
> For portage that's $DISTDIR (/usr/portage/distfiles by default). The
> above sources installation would thus be to ${DISTDIR}/go/${PN}-${SLOT},
> using a path similar to that used by the various live-build eclasses,
> git-r3, etc.I have golang-vcs.eclass (shown already on the list) that will use go get to pull things and put them in /usr/portage/distfiles/go-src; that is the same as a $GOPATH directory, so you would have /usr/portage/distfiles/go-src/$GO_PN. Those would be live sources depending on which vcs upstream is using. If we want to have versions of sources for snapshots, I would suggest another location to store those sources. Debian uses /usr/share/gocode for that, so there would be /usr/share/gocode which could be added to gopath as well. directory our ebuilds would add to GOPATH. I may be able to do that in my golang.eclass. Here's the idea from Debian, as referenced earlier on the list [1]. William [1] http://pkg-go.alioth.debian.org/packaging.html
signature.asc
Description: Digital signature
