Re: inputs vs. native-inputs vs. propagated-inputs

2016-07-10 Thread Chris Marusich
Lukas Gradl writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Lukas Gradl skribis: >> >>> l...@gnu.org (Ludovic Courtès) writes: >>> Leo Famulari skribis: > I _think_ that `gc --references` works by querying the database for a > list of references in the store item you giv

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-21 Thread Lukas Gradl
l...@gnu.org (Ludovic Courtès) writes: > Lukas Gradl skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Leo Famulari skribis: >>> I _think_ that `gc --references` works by querying the database for a list of references in the store item you give it as an argument. I think

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-19 Thread Ludovic Courtès
Lukas Gradl skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Leo Famulari skribis: >> >>> I _think_ that `gc --references` works by querying the database for a >>> list of references in the store item you give it as an argument. I think >>> that the information in the database is created a

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-18 Thread Lukas Gradl
l...@gnu.org (Ludovic Courtès) writes: > Leo Famulari skribis: > >> I _think_ that `gc --references` works by querying the database for a >> list of references in the store item you give it as an argument. I think >> that the information in the database is created after building, by >> scanning t

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-18 Thread Ludovic Courtès
Leo Famulari skribis: > I _think_ that `gc --references` works by querying the database for a > list of references in the store item you give it as an argument. I think > that the information in the database is created after building, by > scanning the files of the package's output in /gnu/store,

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-17 Thread Leo Famulari
On Fri, Jun 17, 2016 at 10:49:59PM +0200, Hartmut Goebel wrote: > >>> If so, how can I as a packager find out if eg. libBBB is only used at > >>> build time and libCCC need to be a propagated input? > > You will need at least a little knowledge about the programs you are > > packaging and how they

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-17 Thread Hartmut Goebel
Hallo Leo, thanks for you answer. Am 12.06.2016 um 21:53 schrieb Leo Famulari: > 'Inputs' do typically get used at run-time, as do propagated-inputs. > > I found it hard to understand the distinctions by reading. It was only > when I had been making packages for a while that I understood. > > I'v

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-12 Thread Leo Famulari
On Sun, Jun 12, 2016 at 05:50:29PM +0200, Hartmut Goebel wrote: > Am 12.06.2016 um 14:38 schrieb 宋文武: > > Hartmut Goebel writes: > >> For for I understand. But then the manual says: > >> > >> ‘native-inputs’ is typically used to list tools needed at > >> build time, but not at

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-12 Thread Hartmut Goebel
Hi, Thanks for your answer Am 12.06.2016 um 14:38 schrieb 宋文武: > Hartmut Goebel writes: >> For for I understand. But then the manual says: >> >> ‘native-inputs’ is typically used to list tools needed at >> build time, but not at run time, such as Autoconf, Automake, >>

Re: inputs vs. native-inputs vs. propagated-inputs

2016-06-12 Thread 宋文武
Hartmut Goebel writes: > Hi, > > I'm a bit confused about the difference between inputs, native-inputs > and propagated-inputs. > > The manual states: > > The distinction between ‘native-inputs’ and ‘inputs’ is > necessary when considering cross-compilation. When >

inputs vs. native-inputs vs. propagated-inputs

2016-06-12 Thread Hartmut Goebel
Hi, I'm a bit confused about the difference between inputs, native-inputs and propagated-inputs. The manual states: The distinction between ‘native-inputs’ and ‘inputs’ is necessary when considering cross-compilation. When cross-compiling, dependencies listed in ‘i