Hi, Ludovic Courtès skribis: > Actually all the profile hooks refer to the native derivation. I’ve looked at it and this problem is surprisingly tricky to address. I’ve tried to address it in an API-compatible way, which meant setting the ‘%current-system’ and ‘%current-target-system’ parameters around the hook calls, but that is ugly, hard to get right (dynamic binding and monadic code really don’t go together well :-/), and actually raises another issue (‘mapm/accumulate-builds’ appears to ignore the initial dynamic bindings for these two parameters). Hacky patch attached to illustrate. So I’m very much tempted to instead require each hook to take ‘system’ and ‘#:target’ arguments and pass them to ‘gexp->derivation’. It’ll break the API, in case someone out there has custom profile hooks (unlikely given that it’s not really documented), but I’d say that’s OK. Thoughts? Ludo’.