Hi,
Also seems that Nix's way only quickly imports the changed layers? And
Guix's always imports the whole thing, at least I think?
What do you mean by “imports the whole thing”?
I'm not sure what exactly happens, so correct me if I'm wrong, however
if I time the different approaches, I
Hello Ricardo,
I greatly agree, it would be an awesome QOL improvement.
Just want to mention that it might be nice to take inspiration from the
Nix dockerTools, since they already have quite a lot of effort put into
this.
Including for example an option called `streamLayeredImage` [1] which
Hello Guix,
There have been a few mentions of rde features on here but were
generally skimmed over, still I think
there's an interesting idea here.
They seem to address a few things, allowing a changing set of services
based on the arguments,
coupling home and system and
passing around
Hello,
just FTR, i don't think that the guix codebase is too bad in this regard.
It's not bad for the slightly initiated, which does still take time, and I
think that front would perhaps benefit from some attention.
My main take away from this was that what I liked mostly about the
Hello guix,
I'll chime in because I've been playing around with this kind of thing
in my channel [1]
for a bit now and perhaps some of the ideas will be deemed useful.
(service+ OS SERVICE [CONF])
(service- OS SERVICE)
(modify-service OS SERVICE UPDATE)
I found that defining a functional
