[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (propagated) 'inputs' depends on 'outputs'?
From: |
zimoun |
Subject: |
Re: (propagated) 'inputs' depends on 'outputs'? |
Date: |
Tue, 16 Jun 2020 17:52:02 +0200 |
Hi Ricardo,
On Tue, 16 Jun 2020 at 17:34, Ricardo Wurmus <rekado@elephly.net> wrote:
> That’s correct. Outputs are buckets into which we drop build
> artifacts. We will build everything with all inputs in one derivation
> and then move stuff into output buckets. This means that you can
> download independent outputs individually, but they are still all the
> result of that *single* derivation. So to build any of the outputs you
> will need to build that derivation, even if it also results in other
> outputs that you don’t care about.
Thank you for the explanations. I understand even if time to time I
feel frustrated to download and/or build a lot of unrelated packages
that I am really interested in. But hey, it is how the thing works. :-)
Now all is clear.
Cheers,
simon