bug#51021: detect loops in module/package graph

Hi, zimoun skribis: > What Mark had implemented [1] works for any directed graph. What do > you mean by "top-level references"? Reference to variables coming from one module of an SCC that appear at the top level of another module in the SCC. >> Chris Baines proposed a patch a while back to r

bug#51021: detect loops in module/package graph

Hi Ludo, On Thu, 7 Oct 2021 at 15:34, Ludovic Courtès wrote: > Mark H Weaver skribis: > > raingloom 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

bug#51021: detect loops in module/package graph

Hi Mark, Mark H Weaver skribis: > raingloom 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 . > > Back in August 201

bug#51021: detect loops in module/package graph

Earlier, I wrote > I've attached a script that I hacked up in 2014 to analyze the Guix > package module dependency graph. Here's the script: ;;; cycle-viewer.scm: a Guix package module dependency graph analyzer ;;; Copyright (C) 2014 Mark H Weaver ;;; ;;; This program is free software: you can

bug#51021: detect loops in module/package graph

Hi, raingloom 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 . Back in August 2014, there was a strongly connected componen

bug#51021: detect loops in module/package graph

I'll be short and blunt, currently it sucks big time whenever you have a loop in your packages. There is no indication other than Guix hanging forever without any output. I don't want to spend my time manually finding loops in graphs, computers are better at that. Sadly I don't know when I'll hav