On Mon, Oct 16, 2017 at 05:38:43PM -0400, Leo Famulari wrote:
> Using the domain name as part of the *upstream* library name is useful
> for upstream authors because of how Go's built-in dependency management
> tools work. Go integrates dependency management into the language and
> the `go` tool it
Leo Famulari skribis:
> On Mon, Oct 16, 2017 at 02:56:38PM +0200, Ludovic Courtès wrote:
>> From the maintainer’s viewpoint, it just stresses that we must keep
>> going with the efforts to improve our build infrastructure. Currently
>> that has only benefited x86, but perhaps now is a good time
Hello,
Leo Famulari writes:
> On Mon, Oct 16, 2017 at 05:38:43PM -0400, Leo Famulari wrote:
>> Using the domain name as part of the *upstream* library name is useful
>> for upstream authors because of how Go's built-in dependency management
>> tools work. Go integrates dependency management into
Hello Hartmut!
Hartmut Goebel writes:
> Hi,
>
> maybe somebody want to work in this puzzle :-)
>
> Last week I played around upgrading the android libs and tools to the
> current release 8.0.0_r17, when I realized that the build-system has
> switched from a Makefile-base to one based on "Android
