python3Packages.ansible: split into ansible and ansible-base, update to 2.10.x #100147
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
This is a mess.
In v2.10 the ansible package was split into collections (
ansible
) and engine (ansible-base
).The
ansible
package requiresansible-base
.The
ansible-base
package holds the executables.This means I cannot introduce
ansible
(the collections) as apropagatedBuildInput
intoansible-base
(the engine), because it would create an inifinite loop. Installing theansible
package, instead ofansible-base
would prevent the executables from theansible-base
package from landing in the PATH.The ansible packagers clearly assume a global python path, where these things just work. Looking for good ideas on how to continue.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)