all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Circular dependencies in gnu/packages, weird error message
Date: Fri, 04 Nov 2016 15:37:52 +0100	[thread overview]
Message-ID: <871syr1fb3.fsf@gnu.org> (raw)
In-Reply-To: <20161104022451.4c7690eb@scratchpost.org> (Danny Milosavljevic's message of "Fri, 4 Nov 2016 02:24:51 +0100")

Hi,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> I cannot import (gnu packages cross-base) in (gnu packages admin) (it gave an incomprehensible-to-me error message [*]). What could be the cause?

Some (gnu packages …) modules were referring to bindings from other
modules at the top level, which doesn’t play well with circular module
dependencies.

Commits fb77c61422ae2d03c0bf655d96b0e88f5f8001da and
bd2e1a8cb07088bdc54b9bb05d9b2e99f78e5b28 work around that.

You should now be able to add #:use-module (gnu packages cross-base) in
admin.scm.

> Since I speculated maybe circular dependencies are the cause (?), I wrote a quick one-off script to find define-module and #:use-module forms and reformat them into Makefile rules. This allowed me to find all the circular dependencies between the modules in gnu/packages.

Fun hack.  :-)

Thanks,
Ludo’.

  reply	other threads:[~2016-11-04 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  1:24 Circular dependencies in gnu/packages, weird error message Danny Milosavljevic
2016-11-04 14:37 ` Ludovic Courtès [this message]
2016-11-04 21:26   ` Danny Milosavljevic
2016-11-06 17:36     ` Ludovic Courtès
2016-11-06 20:50       ` Danny Milosavljevic
2016-11-06 21:29         ` Ludovic Courtès
2016-11-06 22:06           ` Danny Milosavljevic

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=871syr1fb3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dannym@scratchpost.org \
    --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 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.