Stefan Karrmann <s.karrm...@web.de> writes: > Dear all, > > this question was asked several times. But >Computing Guix derivation for > 'x86_64-linux'< annoys really. > > Why do we need this so often? > > Of course, we need this, if we pull a new guix. If we do it, we know that it > takes its time. > > But why do we need it with >guix system reconfigure< etc.pp.? We have a pulled > guix locally and ready. That's the one we want to use! Well, I see that >guix > system reconfigure< pulls new commits. But why? I don't want them.
Would you be able to share some more details about your configuration and setup in general? It is some time since I have last used `guix system reconfigure' -- I only use `guix deploy' these days -- but I have to say I do not recall reconfigure doing a pull. So this might be something specific to your setup? Can you get reproducer in a virtual machine and share the configuration and commands to run? > [..] > OPEN: How to handle local trees (i.e. -L directory)? Well, they add > new branches and leafs, maybe a new forest. They do not change the old > forest at all. I do not think this is accurate. You can use -L to deploy completely custom Guix -- that is how pre-inst-env works when using checkout of the Guix repository. So while I agree that *usually* -L just adds new stuff, it very much *can* change "the old forest". Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
