Open Stack

On 05/09/2016 01:15 PM, Clint Byrum wrote:
> Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700:
>> On Mon, 9 May 2016 09:06:02 -0400
>> Rayson Ho <raysonlogin at gmail.com> wrote:
>>
>>> Since the Go toolchain is pretty self-contained, most people just follow
>>> the official instructions to get it installed... by a one-step:
>>>
>>> # tar -C /usr/local -xzf go$VERSION.$OS-$ARCH.tar.gz
>>
>> I'm pretty certain the humanity has moved on from this sort of thing.
>> Nowadays "most people" use packaged language runtimes that come with
>> the Linux they're running.
>>
> 
> Perhaps for mature languages. But go is still finding its way, and that
> usually involves rapid changes that are needed faster than the multi-year
> cycle Linux distributions offer.
> 
> Also worth noting, is that go is not a "language runtime" but a compiler
> (that happens to statically link in a runtime to the binaries it
> produces...).
> 
> The point here though, is that the versions of Python that OpenStack
> has traditionally supported have been directly tied to what the Linux
> distributions carry in their repositories (case in point, Python 2.6
> was dropped from most things as soon as RHEL7 was available with Python
> 2.7). With Go, there might need to be similar restrictions.

Since this is a forward-facing thing, I think starting with the version
that's in xenial is probably fine for today, yeah? That will be the
version of go that will get installed in the gate starting with this cycle.