[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Design decision behind inputs/native-inputs/propagated-inputs
From: |
Steven Allen |
Subject: |
Re: Design decision behind inputs/native-inputs/propagated-inputs |
Date: |
Thu, 21 Jan 2016 20:30:25 -0500 |
User-agent: |
Mutt/1.5.23.1 (2014-03-12) |
On 01-22-16, Ben Woodcroft wrote:
> On 22/01/16 09:19, Steven Allen wrote:
> >Just to be clear, given:
> >
> > (package
> > (name "foo")
> > (inputs `(("bar", bar)))
> > (native-inputs `(("baz", baz)))
> > ...
> > )
> >
> >If I install "foo", "foo" will **always** be able to use the files in "bar"
> >but will not (may not?) be able to use the files in "baz"?
> That's true for some definition of 'use', yes. If you add foo to your
> profile and it is downloaded from a substitute (as opposed to being built
> from source on your machine), then you'll have to download bar as well, but
> not necessarily baz.
Got it. Thanks.
--
Steven Allen
((Do Not Email <address@hidden>))
signature.asc
Description: PGP signature
- Design decision behind inputs/native-inputs/propagated-inputs, Steven Allen, 2016/01/21
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Ludovic Courtès, 2016/01/21
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Steven Allen, 2016/01/21
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Ben Woodcroft, 2016/01/21
- Message not available
- Message not available
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Steven Allen, 2016/01/21
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Ben Woodcroft, 2016/01/21
- Re: Design decision behind inputs/native-inputs/propagated-inputs,
Steven Allen <=
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Steven Allen, 2016/01/23
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Ludovic Courtès, 2016/01/23
- Re: Design decision behind inputs/native-inputs/propagated-inputs, Steven Allen, 2016/01/23