[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: |
Fri, 10 Jan 2020 13:13:57 +0100 |
Hi Ludo,
On Wed, 8 Jan 2020 at 22:50, Ludovic Courtès <address@hidden> wrote:
> Ricardo Wurmus <address@hidden> skribis:
> > On the other hand: this would need to be an ongoing effort. Newly
> > introduced packages or even new features might create complex module
> > cycles. It sounds tedious to keep track of this and to enforce
> > boundaries.
>
> Yes, I think this is a dead end: glibc could well end up become on
> Haskell (hi, Pandoc!), and then the whole module split effort collapses.
What kind of metrics could help to detect which modules are going to
the wrong way?
For example, would some DAG post-processings help?
All the best,
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, 2020/01/07
- 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,
zimoun <=
Re: Speeding up “guix pull”: splitting modules, Ludovic Courtès, 2020/01/08