From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 51021@debbugs.gnu.org
Subject: bug#51021: detect loops in module/package graph
Date: Thu, 07 Oct 2021 15:28:48 +0200 [thread overview]
Message-ID: <87o881c6b3.fsf@gnu.org> (raw)
In-Reply-To: <87czojkilc.fsf@netris.org> (Mark H. Weaver's message of "Tue, 05 Oct 2021 03:59:00 -0400")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> raingloom <raingloom@riseup.net> writes:
>> I'll be short and blunt, currently it sucks big time whenever you have
>> a loop in your packages.
>
> Agreed. I've been concerned about this problem since the early days of
> Guix. See <https://bugs.gnu.org/18247>.
>
> Back in August 2014, there was a strongly connected component (SCC)
> containing 51 package modules:
Thanks for the analysis and for the updated patch!
Module cycles are something we allow and even rely on, so finding cycles
in itself is not necessarily helpful. What would help is finding cyclic
top-level references, which are those that cause problems, but that’s
another story.
WDYT?
Now, I’m not sure if raingloom was talking about these cycles, or rather
about cycles in the package dependency graph?
Chris Baines proposed a patch a while back to report those, though I
can’t find it anymore. IIRC, the difficulty was in making sure cycle
detection would not be too expensive, and in keeping a readable style.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-10-07 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 0:58 bug#51021: detect loops in module/package graph raingloom
2021-10-05 7:59 ` Mark H Weaver
2021-10-05 8:03 ` Mark H Weaver
2021-10-07 13:28 ` Ludovic Courtès [this message]
2021-10-11 7:49 ` zimoun
2021-10-12 9:47 ` 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=87o881c6b3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51021@debbugs.gnu.org \
--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 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.