all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: Superfly Johnson <superfly.johnson@yahoo.com>, guix-devel@gnu.org
Subject: Re: Go Package with multiple subpackage
Date: Mon, 21 Oct 2024 16:18:56 +0200	[thread overview]
Message-ID: <ZxZi0CnEtNaFkHfs@jurong> (raw)
In-Reply-To: <20241018234328.58f7c0fa@primary_laptop>

Am Fri, Oct 18, 2024 at 11:43:28PM +0200 schrieb Denis 'GNUtoo' Carikli:
> I verified most of the licenses for the dependencies with a combination
> of recursive guix import and manually looking for the ones that weren't
> detected.
> 
> And given the number of dependencies I was told that it was okay to
> have them bundled in.
> 
> As I understand, packaging too many dependencies would create
> complications for the maintenance.

Is that true? It looks opposite to the general Guix philosophy;
once you have invested all the work of checking the licenses, it would
seem a progress to submit the corresponding packages. But maybe Go is
special in that respect; it would be nice to have the Go team's opinion.

Andreas



  reply	other threads:[~2024-10-21 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8f50a338-43e8-4142-90de-fb255686aaca.ref@yahoo.com>
2024-09-22 17:21 ` Go Package with multiple subpackage Superfly Johnson
2024-10-18 21:43   ` Denis 'GNUtoo' Carikli
2024-10-21 14:18     ` Andreas Enge [this message]
2024-10-21 19:32       ` Samuel Christie via Development of GNU Guix and the GNU System distribution.
2024-10-25 22:46       ` Denis 'GNUtoo' Carikli
2024-10-21 17:13   ` Nicolas Graves
2024-09-22 21:30 Sharlatan Hellseher
  -- strict thread matches above, loose matches on Subject: below --
2024-10-26 22:11 Sharlatan Hellseher
2024-10-27 15:14 ` Denis 'GNUtoo' Carikli
2024-10-27 17:56   ` Andreas Enge
2024-10-28 19:53     ` Denis 'GNUtoo' Carikli

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=ZxZi0CnEtNaFkHfs@jurong \
    --to=andreas@enge.fr \
    --cc=GNUtoo@cyberdimension.org \
    --cc=guix-devel@gnu.org \
    --cc=superfly.johnson@yahoo.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.