unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: "Christina O'Donnell" <cdo@mutix.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Golang mudules to follow common grouping
Date: Mon, 5 Feb 2024 19:52:44 +0000	[thread overview]
Message-ID: <CAO+9K5opwMg4HiEe6FF2wFrp-1PVGUNbMRCPdxFAYUuQma8Muw@mail.gmail.com> (raw)
In-Reply-To: <4ad481ec-ce68-a48e-65eb-be1985544680@mutix.org>

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

Hi,

I stick to this flow
- pick a package from golang.scm e.g. go-package-a
- identify destination (any of golang-*.scm)
- place go-package-a to e.g. golang-web.scm in alphabetic order
- remove go-package-a from golang.scm
- by using magit find all authors contributing to go-package-a
- place found copyright headers to golang-web.scm if they are unique
- grep -l -r go-package-a gnu/packages/
- identify if the module(s) missing use-module (gnu packages golang-web),
add if so
- guix build go-package-a
- build all dependent to go-package-a
- make a commit ...
...
repeat as many times as needed.


Batch of 40-50 is a golden median amount to review.

Thanks,
Oleg

[-- Attachment #2: Type: text/html, Size: 1150 bytes --]

  reply	other threads:[~2024-02-05 19:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  0:34 Golang mudules to follow common grouping Sharlatan Hellseher
2024-01-29 23:15 ` Christina O'Donnell
2024-02-05  0:19   ` Christina O'Donnell
2024-02-05 14:00     ` Sharlatan Hellseher
2024-02-05 18:44       ` Christina O'Donnell
2024-02-05 19:52         ` Sharlatan Hellseher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11  9:21 Sharlatan Hellseher
2023-10-10  2:00 Sharlatan Hellseher
2023-10-10  3:52 ` Maxim Cournoyer
2023-10-19  1:34   ` Sharlatan Hellseher
2023-10-15 21:12 ` Wilko Meyer
2023-10-16 18:17   ` Sharlatan Hellseher
2023-10-19  9:40     ` Sharlatan Hellseher
2023-10-30  1:17       ` Sharlatan Hellseher
2024-01-13 21:05         ` Sharlatan Hellseher
2024-01-18 19:36           ` Maxim Cournoyer
2024-01-20 10:01             ` Sharlatan Hellseher
2024-02-13 14:45             ` Sharlatan Hellseher
2024-02-16 15:15               ` Maxim Cournoyer
2024-01-20 11:31           ` Christina O'Donnell
2024-01-20 12:26             ` Sharlatan Hellseher
2024-01-20 19:49               ` Christina O'Donnell
2024-01-20 18:33             ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=CAO+9K5opwMg4HiEe6FF2wFrp-1PVGUNbMRCPdxFAYUuQma8Muw@mail.gmail.com \
    --to=sharlatanus@gmail.com \
    --cc=cdo@mutix.org \
    --cc=guix-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).