all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Troy Figiel <troy@troyfigiel.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>, guix-devel@gnu.org
Cc: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Subject: Re: Initialization of go-team branch.
Date: Fri, 23 Feb 2024 11:13:53 +0100	[thread overview]
Message-ID: <60996869-5c77-4551-b477-78706f0c07aa@troyfigiel.com> (raw)
In-Reply-To: <87zfvr7bvu.fsf@gmail.com>


[-- 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 --]

  reply	other threads:[~2024-02-23 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  9:44 Initialization of go-team branch Sharlatan Hellseher
2024-02-23 10:13 ` Troy Figiel [this message]
2024-02-25 10:09 ` Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60996869-5c77-4551-b477-78706f0c07aa@troyfigiel.com \
    --to=troy@troyfigiel.com \
    --cc=guix-devel@gnu.org \
    --cc=poptsov.artyom@gmail.com \
    --cc=sharlatanus@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.