From: Christina O'Donnell <cdo@mutix.org>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Golang mudules to follow common grouping
Date: Mon, 29 Jan 2024 23:15:51 +0000 [thread overview]
Message-ID: <ca1c9815-7ed1-bdbd-4133-a8bc57f3d500@mutix.org> (raw)
In-Reply-To: <87ede1htac.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2630 bytes --]
Hi Oleg,
> I've pushed the split III to master.
Fantastic work!
> I think you may help! The identification of the group is still human
> decision making process and I'm not sure it may be automated in any point.
I can certainly help with this then. I'll have some free time on Friday and
I can coordinate with you then.
> Each of the module header contains a short annotation which packages it
> expects to have, feel free to improve it to make it even more clear
> for others.
>
> - golang-check
> - golang-web
> - golang-crypto
>
> TBA:
> - golang-compression :: Anything related to that subject, see
> python-compression, java-compression, perl-compression.
>
> - golang-build or golang-extension :: Any low level golang add-ons not
> included in core distribution see <https://pkg.go.dev/golang.org/x> or
> any 0 dependencies high reference modules.
>
> - golang-xyz :: As any other *-xyz module would absorb anything else
> left behind.
This all sounds sensible to me.
>> 1. Put a magic comment above each package that you would like to move.
>> 2. Run a simple script that makes a note of all of these into a
>> to-move-list.
>> 3. Then stash the change with the comments you made (in case you need
>> to change things)
>> 4. Run another script that takes the package list and performs the
>> move in one's repository.
>> 5. Sort out the use-package declarations manually and run tests.
>> 6. When satisfied, stash the change and keep just the use-package
>> changes.
>> 7. Run a final script that loops through all the packages and commits
>> each one in turn.
>> 8. Rebase to suit.
>
> We may extend handy script accelerating committing process, see
> "etc/committer.scm"
Okay, cool, I'll have a look at it on Friday.
>> - I'm not a scheme programmer, but I did use Haskell at university so
>> I'm familiar with thinking in a functional style.
> Me too =), but you still can help by just providing some review to
> existing code base and available packages in golagn.scm and trying to
> identify close group for each of them.
>
>> I'm also imagining some the possibility of having a script that can
>> remove redundant #:use-module's in the future, though I don't know if
>> we care about a few unneeded modules being included.
> The clean up task may be organasied after sort process is completed, having
> not required #:use-module does not hurt too much but for keeping modules
> tidy and fast to load it definitely beneficial.
This makes sense. Not a priority at present but a nice-to
Looking forward to hacking golang.scm to pieces!
Kind regards,
- Christina
[-- Attachment #2: Type: text/html, Size: 7725 bytes --]
next prev parent reply other threads:[~2024-01-29 23:16 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 [this message]
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
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca1c9815-7ed1-bdbd-4133-a8bc57f3d500@mutix.org \
--to=cdo@mutix.org \
--cc=guix-devel@gnu.org \
--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.