[Slackbuilds-users] The state of development/google-go-lang

[fsLeg]

Hopefully, the next -stable releases in the foreseeable future. But the 
way -current is going, it might be anywhere between a year and a few 
more years before Pat announces a beta. While the future is bright, we 
live in the here and now, and, chances are, Google releases go-1.28 
before Slackware-15.1, which would require yet another bootstrapping 
step. I'd choose maintainability even if it's temporary. But whatever 
works for you. If it ain't broken, don't fix it.

I also looked at the SlackBuild Pat uses. He just took the one from SBo, 
except he replaced all bootstrapping steps with using a Google's 
pre-built binary release to build the needed version in just one step. 
Whatever works for him, I guess, the resulting packages are the same anyway.

I looked at commit 4f1f5818531. It was 10 years ago. According to 
Google's published releases, they stopped bundling libraries since 1.20, 
which was 3 years ago. So the `go install` line really only consumes 
space with nothing actually using the built libraries. People will still 
be able to build shared libraries for their projects, they won't be 
linked to the toolchain anyway.

On 5/8/26 00:15, Andrew Clemons wrote:
> Regarding 1 and 2:
> 
> This is mostly just a case of inertia - what started off a one bootstrap
> of 1.19 so we could build 1.20 slowly crept into multiple bootstrap
> versions as the months rolled by with no new stable and golang's 6 month
> release cycle. When I added the 1.19 bootstrap to build 1.20, I did not
> bother trying to detect if there was already a google-go-lang installed
> just always bootstrapped to keep things simple with the idea once the
> next stable was released, we'd just delete that block of the slackbuild
> again and there'd be no other changes to make. It was not my build, so I
> did not want to make sweeping changes. Now, as you've pointed out, with
> more time passing, it's a right mess with 3 bootstraps to get 1.25
> built. I did consider some time along the way adjusting it, but had
> still hoped we could just snip out the bootstrap steps at the beginning
> and leave everything else the same when the next stable release came,
> but now that google-go-lang is in current, this script is only here to
> keep us covered until then.
> 
> Which brings me to point 3 - I don't know the answer. It has been there
> since 4f1f5818531. But considering google-go-lang has been added to
> current, probably not worth changing this slackbuild here now.
> 
> I have a few things that use google-go-lang, hence I have been bumping
> the version - I updated it for 1.26 last week, but I have not submitted
> it yet because its quite disruptive for the weekly update, but I will
> probably do it this week or next.