Re: Golang mudules to follow common grouping

[Christina O'Donnell]

Hi,

Okay that's a better plan :)

> Let's use  Occam's razor for now. We have few common groups,
> the task is to drop use-module (gnu packages golang) for each
> of them by sorting packages into recently introduced modules.
Right, put the dependencies in of golang-web in golang-web (etc.) as 
much as sensibly possible.

How about when a library is used by many packages in more than one 
different modules?

Kind regards
- Christina

On 05/02/2024 14:00, Sharlatan Hellseher wrote:
> Hello,
>
> Thank you for your research on that, I was not expected to go
> far like you did :-)
>
> My short plan was to follow existing naming model which is in
> use for python-*.scm, lisp-*.scm, perl-*scm, java-*.scm.
> I see that golang would need some extra modules in the future
> and comparing with python-*.scm the package base is not big
> yet.
>
> Let's use  Occam's razor for now. We have few common groups,
> the task is to drop use-module (gnu packages golang) for each
> of them by sorting packages into recently introduced modules.
>
> - golang-web.scm
> - golang-check.scm
> - golang-xyz.scm
> - golang-crypto.scm
>
> Thanks,
> Oleg