On Thu, Jun 11, 2015 at 04:39:05PM -0700, Zac Medico wrote:
> On 06/11/2015 11:43 AM, William Hubbs wrote:
> > On Thu, Jun 11, 2015 at 08:58:37AM -0700, Andrew Udvare wrote:
> >>
> >>> On 2015-06-11, at 08:38, William Hubbs wrote:
> >>>
> >>> this eclass is meant to provide a common src_compile fu
On 06/11/2015 11:43 AM, William Hubbs wrote:
> On Thu, Jun 11, 2015 at 08:58:37AM -0700, Andrew Udvare wrote:
>>
>>> On 2015-06-11, at 08:38, William Hubbs wrote:
>>>
>>> this eclass is meant to provide a common src_compile function for
>>> packages written in the Go programming language.
>>>
>>>
On Thu, Jun 11, 2015 at 08:58:37AM -0700, Andrew Udvare wrote:
>
> > On 2015-06-11, at 08:38, William Hubbs wrote:
> >
> > this eclass is meant to provide a common src_compile function for
> > packages written in the Go programming language.
> >
> > Let me know what you think.
> >
>
> I am wo
> On 2015-06-11, at 08:38, William Hubbs wrote:
>
> this eclass is meant to provide a common src_compile function for
> packages written in the Go programming language.
>
> Let me know what you think.
>
I am wondering about bug 503324 and the issue of needing to create a GOROOT
with everythi
All,
It turns out that we do need a second eclass for Go packages.
this eclass is meant to provide a common src_compile function for
packages written in the Go programming language.
Let me know what you think.
Thanks,
William
# Copyright 1999-2015 Gentoo Foundation
# Distributed under the ter
