Initialization of go-team branch.

Initialization of go-team branch.

[Sharlatan Hellseher]

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]


Hello Guix!

After intitiating go-team branch (inspired by the rust-team) I started
pushing reviwed patches to it, which may require a full Golang rebuild.
My future plan is to update the existing Golang ecosystem to recent
versions, as most of the packages are quite dated (2-5 years old).

As an intial work golang-*.scm submodules are introduces and some
packages were extracted from golang.scm and placed into logical modules.

- golang-build.scm
- golang-check.scm
- golang-compression.scm
- golang-crypto.scm
- golang-web.scm
- golang-xyz.scm

I have CC'd Troy and Artyom as they are actively working on Golang updates.

Following these threads:
- https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00026.html
- https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00128.html

I might need some guidance on the following topics:
- Do I need to rebase to master or merge master into go-team while
  working on it?
- What is the approximate merge into master cycle?
- Do I need to send patches to guix-patches@gnu.org even if I intend to
  push them to the go-team branch?

After reviewing:
- #69205 [PATCH] gnu: Add go-1.22 and its standard library.
- #68300 [PATCH] gnu: Remove go-1.14.
- #69015 [PATCH 0/2] Deprecate the go-etcd-io-bbolt variable,

I rebased on the latest master, then merged master, and finally pushed
to the go-team branch.

--
Oleg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: Initialization of go-team branch.

[Troy Figiel]

[-- Attachment #1.1.1: Type: text/plain, Size: 2269 bytes --]

Hi Oleg,

That's awesome! I don't have much to add, except that it might be good
to sync on what we would like to achieve now that the go-team branch exists.

I was planning on working through some of the points I proposed here:

https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00054.html

(I accidentally created a separate thread, because I didn't reply to you
directly.)

What I would love to implement soon are the test-flags. This should be a
rather straightforward change, as we already have the build-flags.
Nonetheless, it would allows us to skip individual tests (for go >=1.20)
or set higher timeouts. Unfortunately, the past week has been rather
busy for me though.

Best wishes,

Troy

On 2024-02-23 10:44, Sharlatan Hellseher wrote:
> 
> Hello Guix!
> 
> After intitiating go-team branch (inspired by the rust-team) I started
> pushing reviwed patches to it, which may require a full Golang rebuild.
> My future plan is to update the existing Golang ecosystem to recent
> versions, as most of the packages are quite dated (2-5 years old).
> 
> As an intial work golang-*.scm submodules are introduces and some
> packages were extracted from golang.scm and placed into logical modules.
> 
> - golang-build.scm
> - golang-check.scm
> - golang-compression.scm
> - golang-crypto.scm
> - golang-web.scm
> - golang-xyz.scm
> 
> I have CC'd Troy and Artyom as they are actively working on Golang updates.
> 
> Following these threads:
> - https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00026.html
> - https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00128.html
> 
> I might need some guidance on the following topics:
> - Do I need to rebase to master or merge master into go-team while
>   working on it?
> - What is the approximate merge into master cycle?
> - Do I need to send patches to guix-patches@gnu.org even if I intend to
>   push them to the go-team branch?
> 
> After reviewing:
> - #69205 [PATCH] gnu: Add go-1.22 and its standard library.
> - #68300 [PATCH] gnu: Remove go-1.14.
> - #69015 [PATCH 0/2] Deprecate the go-etcd-io-bbolt variable,
> 
> I rebased on the latest master, then merged master, and finally pushed
> to the go-team branch.
> 
> --
> Oleg

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6367 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Initialization of go-team branch.

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]

On Fri, Feb 23, 2024 at 09:44:53AM +0000, Sharlatan Hellseher wrote:
> 
> Hello Guix!
> 
> After intitiating go-team branch (inspired by the rust-team) I started
> pushing reviwed patches to it, which may require a full Golang rebuild.
> My future plan is to update the existing Golang ecosystem to recent
> versions, as most of the packages are quite dated (2-5 years old).
> 
> As an intial work golang-*.scm submodules are introduces and some
> packages were extracted from golang.scm and placed into logical modules.
> 
> - golang-build.scm
> - golang-check.scm
> - golang-compression.scm
> - golang-crypto.scm
> - golang-web.scm
> - golang-xyz.scm
> 
> I have CC'd Troy and Artyom as they are actively working on Golang updates.
> 
> Following these threads:
> - https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00026.html
> - https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00128.html
> 
> I might need some guidance on the following topics:
> - Do I need to rebase to master or merge master into go-team while
>   working on it?

In general a wip- branch is expected to be rebased and otherwise it's
expected to merge. IMO for a team branch it should be expected that the
team knows what's going on, but I can see how it would get confusing
quickly with multiple teams.

> - What is the approximate merge into master cycle?

When the branch seems good then you send a patch to guix-patches with
The Magic Words™¹ which will cause qa.guix.gnu.org to start building the
branch, once the other team branches ahead of it are finished merging.
As far as when, whenever it seems like its ready, at whatever cadence
you're (as the team and/or the steward in charge of shepherding the
merge through is) happy with.

> - Do I need to send patches to guix-patches@gnu.org even if I intend to
>   push them to the go-team branch?

In general it should follow the same standard as other patches for Guix.
In practice people filter for their own interests and hope someone else
will take a look at any others.

> After reviewing:
> - #69205 [PATCH] gnu: Add go-1.22 and its standard library.
> - #68300 [PATCH] gnu: Remove go-1.14.
> - #69015 [PATCH 0/2] Deprecate the go-etcd-io-bbolt variable,
> 
> I rebased on the latest master, then merged master, and finally pushed
> to the go-team branch.

Also can you pull in the patch from bug#67505? Thanks.

¹ I have to look up the phrasing each time.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]