bug#37586: Import cycles in unrelated packages should not be an error

2019-10-06 Thread pelzflorian (Florian Pelz)
On Sun, Oct 06, 2019 at 12:00:27PM +0200, Ludovic Courtès wrote: > "pelzflorian (Florian Pelz)" skribis: > > Is it possible to make import cycles not an error in Guix packages? > > Unfortunately no, it’s fundamentally impossible. When you have: > > (define-module (a) #:use-module (b)) >

bug#37586: Import cycles in unrelated packages should not be an error

2019-10-06 Thread Ludovic Courtès
Hi Florian, "pelzflorian (Florian Pelz)" skribis: > I am annoyed by another import cycle similar to > in an unfinished package I’m > writing. They needlessly complicate packaging and make packagers > split modules that logically should not be split. I

bug#37586: Import cycles in unrelated packages should not be an error

2019-10-02 Thread pelzflorian (Florian Pelz)
I am annoyed by another import cycle similar to in an unfinished package I’m writing. They needlessly complicate packaging and make packagers split modules that logically should not be split. Is it possible to make import cycles not an error in Guix