Dear all,
Ansible project was significantly restructured after v2.9.
Starting with ansible-2.10, the project was split into the core engine
(called ansible-base in v2.10, and renamed to ansible-core in v2.11),
which contains essential code needed to run collections and
ansible collections, e.g. community.aws, community.vmware etc.
Since v2.10 what is called ansible is a python package which contains selected
list of ansible collections and depends on ansible-core package:
https://pypi.org/project/ansible-core/
https://pypi.org/project/ansible/
The core enginge and collections have different versioning schemes:
ansible v3 depends on ansible-core v2.10 and ansible v4 depends on
ansible-core v2.11.
More on ansible project restructurization:
https://www.ansible.com/blog/ansible-3.0.0-qa
Ansible Collections Overview:
https://github.com/ansible-collections/overview
Trying to keep ansible v4 port as close as possible to v2.9, I tried to keep
the html docs, but finally gave up: the tooling used for docs/changelogs
generation includes dozen of python packages, some of them are useless for
anything but ansible docs generation:
new ports:
devel/{py-aiofiles,py-asyncio-pool,py-asynctest,py-pydantic}
textproc/{py-antsibull,py-antsibull-changelog,py-perky,py-rstcheck,
py-semantic-version,py-twiggy}
updates required for:
devel/{py-pluggy,py-sh,py-tox}
I don't think juice worth the squeeze trying to deal with all this mess
to get ansible html docs package. Most people read the docs online.
I also removed the .rst docs and changelogs from the collections, it was
~1/2 of the PLIST, I don't see it very useful there.
Please find the updated ansible port attached along with its dependencies.
I'm looking for comments/OK's.
In my environment the upgrade was smooth, no changes to the custom
roles/playbooks were needed, I have it running it with various
OpenBSD/Linux/Windows targets, everything is fine.
--
With best regards,
Pavel Korovin
No comments:
Post a Comment