Hi again,
Thanks Ricardo for the reminder. :-)
Christopher Baines skribis:
> I've included a very rough patch which detects and informs the user what
> has happened, this is an example of what this looks like (with a version
> of the wip-rails branch I've broken):
>
>
> $ guix build ruby-rails
Hi Ludo,
Christopher wrote this:
>>> I'm not particularly fond of the implementation, because the
>>> package-derivation function is called from expand-input called from
>>> bag->derivation, the information about the part of the graph that has
>>> been traversed is passed through each function.
Hello!
Ricardo Wurmus skribis:
>> I've had this issue for a while now, while adding some packages, I'll
>> create a loop in the package graph, which causes Guix to just loop
>> infinitely when trying to generate derivations.
>
> this is a great initiative. I’ve been having this issue in the pas
Ricardo Wurmus writes:
>> I've had this issue for a while now, while adding some packages, I'll
>> create a loop in the package graph, which causes Guix to just loop
>> infinitely when trying to generate derivations.
>
> this is a great initiative. I’ve been having this issue in the past as
> w
2018-02-12 16:30 GMT+01:00 Ricardo Wurmus :
>
> Hi,
>
> > I've had this issue for a while now, while adding some packages, I'll
> > create a loop in the package graph, which causes Guix to just loop
> > infinitely when trying to generate derivations.
>
> this is a great initiative. I’ve been havi
Hi,
> I've had this issue for a while now, while adding some packages, I'll
> create a loop in the package graph, which causes Guix to just loop
> infinitely when trying to generate derivations.
this is a great initiative. I’ve been having this issue in the past as
well, and I’d really like Gui