[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Speeding up “guix pull”: splitting modules
From: |
zimoun |
Subject: |
Re: Speeding up “guix pull”: splitting modules |
Date: |
Tue, 7 Jan 2020 19:37:25 +0100 |
Hi Ricardo,
On Sun, 5 Jan 2020 at 21:38, Ricardo Wurmus <address@hidden> wrote:
> Gábor once suggested an iterative approach of identifying the most
> important nodes in the package graph that should be moved to their own
> modules, so that we would end up with a package graph that looks less
> like a hair ball. I think it would useful to get a better view on the
> relationships between modules.
I am not sure to correctly understand. What does it mean "the most
important nodes in the package graph"?
Does "important node" mean a package which appears as inputs in a lot
of other packages?
Cheers,
simon
- Speeding up “guix pull”: splitting modules, Ricardo Wurmus, 2020/01/05
- Re: Speeding up “guix pull”: splitting modules, Andy Wingo, 2020/01/06
- Re: Speeding up “guix pull”: splitting modules,
zimoun <=
- Re: Speeding up “guix pull”: splitting modules, Gábor Boskovits, 2020/01/07
- Re: Speeding up “guix pull”: splitting modules, zimoun, 2020/01/10
- Re: Speeding up “guix pull”: splitting modules, Gábor Boskovits, 2020/01/10
- Re: Speeding up “guix pull”: splitting modules, zimoun, 2020/01/10
- Re: Speeding up “guix pull”: splitting modules, Ludovic Courtès, 2020/01/11
- Re: Speeding up “guix pull”: splitting modules, zimoun, 2020/01/20
Re: Speeding up “guix pull”: splitting modules, Ludovic Courtès, 2020/01/08
Re: Speeding up “guix pull”: splitting modules, Ludovic Courtès, 2020/01/08