all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Maxime Devos" <maximedevos@telenet.be>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Lars-Dominik Braun" <lars@6xq.net>
Cc: 57861@debbugs.gnu.org
Subject: [bug#57861] [PATCH] gnu: Add ultrastar-deluxe.
Date: Mon, 17 Oct 2022 14:28:52 +0100	[thread overview]
Message-ID: <CNO8FR0URQ5P.3TYKUWGCL0Y5I@guix-framework> (raw)
In-Reply-To: <4cdb853b-accb-02a5-5f39-e14994dfcb8d@telenet.be>

On Mon Oct 17, 2022 at 2:25 PM BST, Maxime Devos wrote:
> That's still a circular dependency.  Why import (gnu packages pascal) 
> when you don't need it (e.g. when installing another, non-pascal, 
> package)?  There is some bug report on the excessive dependencies among 
> Guix modules with some proposed solutions.

Wouldn't using #:autoload be a cleaner way that still lazily resolves the variables?

    -- (




  reply	other threads:[~2022-10-17 13:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 13:37 [bug#57861] [PATCH] gnu: Add ultrastar-deluxe Lars-Dominik Braun
2022-09-18  9:39 ` Maxime Devos
2022-09-21 11:52   ` [bug#57861] [PATCH v2] " Lars-Dominik Braun
2022-10-17  8:33     ` [bug#57861] [PATCH] " Ludovic Courtès
2022-10-17 13:25       ` Maxime Devos
2022-10-17 13:28         ` ( via Guix-patches via [this message]
2022-10-17 13:37           ` Maxime Devos
2022-10-17 16:44         ` Ludovic Courtès
2022-10-17 17:26           ` Maxime Devos
2022-10-17  8:35     ` Ludovic Courtès
2022-10-18  7:56       ` Lars-Dominik Braun
2022-10-18 12:44         ` Maxime Devos
2022-10-19 11:09           ` [bug#57861] [PATCH v2] " Lars-Dominik Braun
2022-11-07 22:59             ` bug#57861: [PATCH] " Ludovic Courtès
2022-10-18 12:49         ` [bug#57861] " Maxime Devos
2022-09-18 12:26 ` Maxime Devos
2022-11-07 21:41 ` Jonathan Brielmaier

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=CNO8FR0URQ5P.3TYKUWGCL0Y5I@guix-framework \
    --to=guix-patches@gnu.org \
    --cc=57861@debbugs.gnu.org \
    --cc=lars@6xq.net \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=paren@disroot.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.