Re: Design decision behind inputs/native-inputs/propagated-inputs

Steven Allen skribis: > Can anyone tell me what's going on here or point me to the relevant > documentation? Specifically, why does the daemon (assuming guix-daemon) > need to see what store items the package refers to? At the end of a build, guix-daemon scans all the

Re: Design decision behind inputs/native-inputs/propagated-inputs

Hi Steven, On 22/01/16 02:08, Steven Allen wrote: On 01-21-16, Ludovic Courtès wrote: In short, the distinction between ‘native-inputs’ and ‘inputs’ exists solely because Guix supports cross-compilation. Otherwise it would be unneeded. Propagated inputs are a way to manually say: “I want

Design decision behind inputs/native-inputs/propagated-inputs

All, I just attended David Thompson's talk about Guix and asked some questions about the difference between inputs, propagated-inputs, and native-inputs. I believe I now understand what each does but am unclear as to why. Currently, I use Arch. On Arch, we have makedepends and depends where only