Hello,
What an interesting read. Well done, Ludo!
Nicolò Balzarotti writes:
> Interesting blog post, thanks!
> I found a typo:
> /remove-eval/remote-eval/
Me too: s/more of hint/more of a hint/
-- Tim
Hi Ludo!
Interesting blog post, thanks!
I found a typo:
/remove-eval/remote-eval/
Thanks, Nicolò
Ludovic Courtès writes:
> Hello Guix!
>
> I wrote about the recent changes in support of grafts in this post:
>
> https://guix.gnu.org/blog/2020/grafts-continued/
>
> Feedback welcome!
>
> Ludo’.
Hello Guix!
Ludovic Courtès skribis:
> To address that, I think we need a better way to handle “dynamic
> dependencies”. The ‘wip-build-accumulator’ branch does that by taking
> advantage of ‘with-build-handler’. On that branch, grafts no longer use
> substitute info. Instead, they just build
I went ahead and merged the guts of ‘wip-grafts’. This changes the ABI,
so make sure to run:
make clean-go && make
> However, the ‘graft-derivation’ procedure is not recursive: it grafts
> the derivation you give it, but doesn’t graft its dependencies.
This problem is not addressed yet, but I
The current status of ‘wip-grafts’ is that it works, there’s no
performance issue, etc.
However, the ‘graft-derivation’ procedure is not recursive: it grafts
the derivation you give it, but doesn’t graft its dependencies. Thus,
only direct references are grafted, which isn’t so great:
$ guix g
Mark H Weaver skribis:
> If you want a real example, upstream bash is at 4.3.30, whereas we only
> have 4.3.27.
Yes, I have it in my working tree, and will push shortly. :-)
Ludo’.
l...@gnu.org (Ludovic Courtès) writes:
> I pushed ‘wip-grafts’, a branch that implements “grafts.”
>
> Normally security updates deep in the DAG, such as an update of Bash or
> libc, cause a rebuild of everything, which can some time, as we’ve seen
> lately.
>
> The idea of grafts is to graft the
