On Sat, Oct 16, 2021 at 10:02:38AM -0400, Nico Kadel-Garcia wrote:
it could have made good sense, and still would, for the "ansible"
package to be what is now being colloquially referred to as
"ansible-core", but for which the published upstream git repo is still
https://github.com/ansible/ansible, and which is and will remain
accessible as a github release tarball with the old numbering. The
pypi.org published "ansible-core" is a republication of that repo with
a new name duck-taped on it. Fragmenting out the bulky and potentially
dynamic set of tools that are now in the "galaxy collections" suite
makes some sense, but the result is that to get any of the core
modules like "ansible.posix" we wind up including 573 Megabytes of
unneeded and unwelcome debris in
/usr/lib/python3.6/site-packages/ansible_collections. Very few of us
need more than 10% of the list
If you don't need more, don't install 'ansible'. Just install
ansible-core and use galaxy or seperate packaged collections to install
just what you need.
There is no specific source repository for the
"ansible_collections"
tarball, as best I can tell. The list of modules selected from the
galaxy collection is very large, but incomplete and I've not seen any
criteria for what goes in that tarball and what does not. Have you
seen any?
Yes, but I can't seem to find it now. ;(
Basically it was agreeing to use symantic versioning and agreeing to
release on the same schedule as the rest, etc. I don't know if there's
further requirements now. I'll find that doc and post it, but kinda
weekending now. ;)
...snip...
kevin