[Nix-dev] Ideas for systematically avoiding unwanted runtime dependencies

[Tomasz Kontusz]

On 08/27/2015 12:15 AM, Daniel Peebles wrote:
> Right now I'm struggling with my image pulling in gcc because it 
> legitimately depends on icu4c, which mysteriously retains a runtime 
> dependency on gcc. Regardless of specifics, individual packages can 
> usually be fixed to reduce their runtime footprint, but I'm looking 
> for ideas for how to do so in a systematic manner, so we don't just 
> notice these things by accident and fix them one by one. Does anyone 
> have any thoughts?
For specific known-problematic packages we could use allowedReferences 
(see http://nixos.org/nix/manual/#sec-advanced-attributes) to make sure 
we have control over runtime dependencies.

I'm not sure how that would work with multiple outputs, but if it was 
per-output we could even use it by default (most packages don't need 
references to gcc in their default output :-)).

> Also, multiple outputs won't really help with this problem because 
> there's nothing stopping these packages from retaining references to 
> many of our outputs.
>
> Thanks,
> Dan
>
>
> [1] https://github.com/NixOS/nixpkgs/issues/5895
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20150827/129d6075/attachment.html