From: zimoun <zimon.toutoune@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Speeding up “guix pull”: splitting modules
Date: Fri, 10 Jan 2020 13:53:38 +0100 [thread overview]
Message-ID: <CAJ3okZ3Rq72orHjg85o-O2PRTd6AEVWUUpJm62qWNOo_WkEJYg@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=pgK9MJWKwgFqS3XL1G27Zb40=G1Q_RuM3F-7NEPJzVdhA@mail.gmail.com>
Hi Gábor,
On Fri, 10 Jan 2020 at 13:42, Gábor Boskovits <boskovits@gmail.com> wrote:
> > The modules graph (DAG) is already available. :-)
>
> The main problem here is that the modules do not form a DAG.
> There are circular dependencies between the modules.
> If those were not, then modular build would be possible, but because of
> the spaghetti we are forced to build these together.
Maybe we have a naming problem. :-)
I agree that it is not an Acyclic graph and if I understand you
correctly it is because there are cycles that the mess starts.
Using the Directed properties (but not required in fact, whatever :-),
traversing the graph detects the cycle. It is more or less what it is
done in the function `guix/import/utils.scm (topological-sort)`.
So knowing where the cycles are could help to transform the DaG (not
fully acyclic yet) to a DAG. :-)
All the best,
simon
next prev parent reply other threads:[~2020-01-10 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 20:37 Speeding up “guix pull”: splitting modules Ricardo Wurmus
2020-01-06 9:11 ` Andy Wingo
2020-01-07 18:37 ` zimoun
2020-01-07 20:14 ` Gábor Boskovits
2020-01-10 12:09 ` zimoun
2020-01-10 12:42 ` Gábor Boskovits
2020-01-10 12:53 ` zimoun [this message]
2020-01-11 23:29 ` Ludovic Courtès
2020-01-20 17:44 ` zimoun
2020-01-08 21:50 ` Ludovic Courtès
2020-01-10 12:13 ` zimoun
2020-01-10 19:02 ` Ricardo Wurmus
2020-01-08 21:57 ` Ludovic Courtès
[not found] ` <87zhenp01v.fsf@cbaines.net>
2020-01-19 21:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3Rq72orHjg85o-O2PRTd6AEVWUUpJm62qWNOo_WkEJYg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=boskovits@gmail.com \
--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.