Re: Naming of native-inputs/inputs/propagated-inputs

2019-07-23 Thread Ben Sturmfels
On Tue, 23 Jul 2019, Ricardo Wurmus wrote: > The difference between “native-inputs” and “inputs” is not about whether > they are needed at build time or runtime. The difference only really > comes into play when cross-building. “native-inputs” must be of the > host architecture, while “inputs” a

Re: Naming of native-inputs/inputs/propagated-inputs

2019-07-23 Thread Ricardo Wurmus
Hi Ben, > I know this is superficial, but I wonder if these names could be refined > to better communicate their use. What about: > > | Currently | Possible new name | > |---+---| > | native-inputs | build-inputs | > | inputs| runtime-

Naming of native-inputs/inputs/propagated-inputs

2019-07-22 Thread Ben Sturmfels
Hi Folks, On the rare occasion I dip into Guix packaging, I rely on Pierre's tutorial[1] because it has the least confusing definition of "native-inputs" "inputs" and "propagated-inputs". Before that tutorial existed, I don't think I properly understood the difference. I know this is superficial,