On Wed, Jul 22, 2015 at 05:19:11PM -0500, William Hubbs wrote:
> All,
>
> after some testing, i decided that the eclass should make both the
> golibdir and the prefixed version of it available with functions.
>
> The reason for this is that the prefixed golibdir should be part of
> GOPATH when bu
On Thu, Jul 23, 2015 at 12:37:59AM +0200, Manuel Rüger wrote:
> On 23.07.2015 00:19, William Hubbs wrote:
> > All,
> >
> > after some testing, i decided that the eclass should make both the
> > golibdir and the prefixed version of it available with functions.
> >
> > The reason for this is that t
On 23.07.2015 00:19, William Hubbs wrote:
> All,
>
> after some testing, i decided that the eclass should make both the
> golibdir and the prefixed version of it available with functions.
>
> The reason for this is that the prefixed golibdir should be part of
> GOPATH when building packages.
>
>
All,
after some testing, i decided that the eclass should make both the
golibdir and the prefixed version of it available with functions.
The reason for this is that the prefixed golibdir should be part of
GOPATH when building packages.
The functions are get_golibdir and get_golibdir_gopath.
He
On Wed, Jul 22, 2015 at 7:36 PM, William Hubbs wrote:
> Let me know what you think.
I tried to use your eclass recently, but it failed with this error:
* Call stack:
*ebuild.sh, line 765: Called __ebuild_main 'compile'
* phase-functions.sh, line 968: Called __dyn_compile
*
unsubscribe
On Thu, Jul 23, 2015 at 3:36 AM, William Hubbs wrote:
> All,
>
> the following backward compatible update makes the go package path
> visible to ebuilds and separates the code that installs Go packages into
> its own function which can be called by ebuilds.
>
> Let me know what you
All,
the following backward compatible update makes the go package path
visible to ebuilds and separates the code that installs Go packages into
its own function which can be called by ebuilds.
Let me know what you think.
William
Index: golang-build.eclass
==
