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: Sat, 20 Jan 2024 12:26:22 +0000 [thread overview]
Message-ID: <CAO+9K5qq3QXcKJJKSEjNj5skwXhXhSOpzvGvDzR9fezOq=XbNA@mail.gmail.com> (raw)
In-Reply-To: <5d4663d5-8f33-0f2c-0a37-4d9946b04c27@mutix.org>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Hi Christina,
> Would it be more organized if they was just one order: either
> in alphabetical order or grouped by function? My suggestion
> would be to use the file split to group by function and then sort
> each file alphabetically. Do you know how it is arranged for other
> languages?
I've added comments in commentary section in the top of the file
asking to keep packages alphabetically sorted seen in
julia-xyz.scm as well. python-*.scm ordered semi random grouped
closer to package purpose which require more thinking where to put a new
one : -)
> Another question I have: Is there any tooling that can help big package
> migrations like this go faster? Eg. a script to split one big diff into
> individual package moves with appropriate change-log entries.
Good point her, I did manual split, with Emacs keyboard macros,
magit history scan for copyright lines and manual check where
package was used to include new module name.
The split into golang-crypto is in review now and there would be 2 more
common grouping: golang-compression and golang-build (or
golang-extension). Rest packages which are hard to determine a
group wound go to generic golang-xyz sorted alphabetically.
Let me know your tooling which you familiar with I might think
about some sort of automation.
Thanks,
Oleg
[-- Attachment #2: Type: text/html, Size: 2478 bytes --]
next prev parent reply other threads:[~2024-01-20 12:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 2:00 Golang mudules to follow common grouping 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 [this message]
2024-01-20 19:49 ` Christina O'Donnell
2024-01-20 18:33 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 9:21 Sharlatan Hellseher
2024-01-29 0:34 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
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='CAO+9K5qq3QXcKJJKSEjNj5skwXhXhSOpzvGvDzR9fezOq=XbNA@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 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.