From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Golang mudules to follow common grouping
Date: Thu, 19 Oct 2023 10:40:37 +0100 [thread overview]
Message-ID: <CAO+9K5r45qjaVA1TOb7A9mWcYdiw1rArHq2+ifncf5suFz2q3A@mail.gmail.com> (raw)
In-Reply-To: <CAO+9K5pWqm6-fz7y0cDX_tj6ChLk+nNP2ULeV5umLBeQ39xU6w@mail.gmail.com>
Hi,
I've accidentally included other patch to this series. I've re-sent it under the
new issue number https://issues.guix.gnu.org/66627.
Thanks,
Oleg
On Mon, 16 Oct 2023 at 19:17, Sharlatan Hellseher <sharlatanus@gmail.com> wrote:
>
> Hi,
>
> I'm about to create golang-check and golang-build modules, which both are core and would be in used by others. As Maxim mentioned, the most time consumption task would be migrating copyrights header properly.
>
> On Sun, 15 Oct 2023, 22:25 Wilko Meyer, <w@wmeyer.eu> wrote:
>>
>>
>> Hi,
>>
>> Sharlatan Hellseher <sharlatanus@gmail.com> writes:
>>
>> > I think it's time to split (gnu packages golang) into some logical groups, see
>> > Python, Lisp for example.
>> >
>> > Thoughts?
>>
>> IMHO this sounds like a good idea as it would improve the
>> maintainability of golang packages in the long run. We have 487 package
>> definitions right now:
>>
>> (~/devel/guix-devel/gnu/packages) λ rg -c 'define-public' golang.scm
>> 487
>>
>> which already seems quite laborous to split into logical groups (while
>> getting the copyright information right as well and maintaining the
>> gitlog history etc.); so it probably classifies as a task that should be
>> tackled sooner than later as it'll cause more work over time the more
>> golang packages exist.
>>
>> --
>> Kind regards,
>>
>> Wilko Meyer
>> w@wmeyer.eu
--
… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.
next prev parent reply other threads:[~2023-10-19 6:41 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 [this message]
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
-- 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
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+9K5r45qjaVA1TOb7A9mWcYdiw1rArHq2+ifncf5suFz2q3A@mail.gmail.com \
--to=sharlatanus@gmail.com \
--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).