unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: mhw@netris.org
Cc: 18247-done@debbugs.gnu.org, Eric Bavier <ericbavier@gmail.com>
Subject: bug#18247: Cyclic dependencies in (gnu package *) modules
Date: Thu, 28 Aug 2014 11:41:12 +0200	[thread overview]
Message-ID: <874mwxeytj.fsf@gnu.org> (raw)
In-Reply-To: <87fvh1lsnh.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 12 Aug 2014 15:54:58 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> Another possibility, probably better, would be to split base into two
> modules: one that exports the normal package definitions (the first page
> of base.scm, in terms of C-x n p), and one that exports %final-inputs
> and related stuff (the second page).  Normally the latter will not have
> to be used directly, except by (guix build-system gnu) and related
> stuff.

Commit bdb3695 does that.

It helps a bit already, in that, for instance, adding Guile-Charting and
its dependency on (gnu packages gtk) would have been impossible before,
but here does not cause any problems.

Comments welcome!

I’m closing this bug but we’ll certainly have to keep an eye on it, so
feel free to reopen as you see fit.

Thanks,
Ludo’.

  parent reply	other threads:[~2014-08-28  9:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 20:05 bug#18247: Cyclic dependencies in (gnu package *) modules mhw
2014-08-11 20:49 ` mhw
2014-08-11 21:07 ` Ludovic Courtès
2014-08-11 23:59   ` Mark H Weaver
2014-08-12  3:28     ` mhw
2014-08-12  7:31       ` mhw
2014-08-12 13:54         ` Ludovic Courtès
2014-08-12 20:53           ` Eric Bavier
2014-08-13 18:55             ` Mark H Weaver
2014-08-13 22:09             ` Ludovic Courtès
2014-08-16  6:00               ` Eric Bavier
2014-08-16  9:11                 ` Ludovic Courtès
2014-08-28  9:41           ` Ludovic Courtès [this message]
2014-08-12 11:05     ` Ludovic Courtès

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=874mwxeytj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=18247-done@debbugs.gnu.org \
    --cc=ericbavier@gmail.com \
    --cc=mhw@netris.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).