![]() Albeit counter-intutive, the `propagatedBuildInputs`
mechanism and the corresponding package files in
`nix-support/propagated-build-inputs`
can form a dependency cycle.
This can happen if a package adds itself to this file,
or if multiple outputs of one derivation reference each other.
An example for this is the `patchPpdFilesHook`:
In its mission to collect dependency packages with binaries
that might be required by the dependent package to be created,
it sometimes picks up the dependent package itself.
This indicates that if a file of the dependent package
is used, the package itself should also be installed.
In the case of a multiple output package,
it is also possible that two outputs depend on each other,
creating a dependency cycle.
Since commit
|
||
---|---|---|
.. | ||
catch_conflicts | ||
conda | ||
cpython | ||
hooks | ||
manylinux | ||
pypy | ||
python2 | ||
rustpython | ||
tests | ||
update-python-libraries | ||
default.nix | ||
mk-python-derivation.nix | ||
passthrufun.nix | ||
python-packages-base.nix | ||
run_setup.py | ||
setup-hook.nix | ||
setup-hook.sh | ||
sitecustomize.py | ||
tests.nix | ||
with-packages.nix | ||
wrap-python.nix | ||
wrap.sh | ||
wrapper.nix |