mirror of
https://github.com/NixOS/rfcs.git
synced 2025-12-20 16:01:16 +01:00
Add small ()
This commit is contained in:
parent
d1cadb6b65
commit
a570b1a9ae
1 changed files with 1 additions and 1 deletions
|
|
@ -120,7 +120,7 @@ environment is used even by builders, not only user facing Python environments.
|
|||
`propagatedBuildInputs` and not regular `buildInputs`. I think this was done so
|
||||
in the past so it'd be easy to know how to wrap them? Declarative wrappers
|
||||
won't require runtime-env-requiring deps to be only in `propagatedBuildInputs`
|
||||
or `buildInputs` - it should pick such deps from both lists. Hence, I think it
|
||||
or `buildInputs` - it should pick such deps from both lists. Hence, (I think) it
|
||||
should be possible to make Python's static builds consistent with other
|
||||
ecosystems.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue