On Tue, Jul 5, 2022 at 8:30 AM Brian Coca <
bc...@redhat.com> wrote:
>
> Also note that the 'ansible core' and the 'ansible targets' have
> different dependencies, core in general requires newer python and
> keeps compatibility for modules to execute on older pythons on the
> target.
Frankly, the current "ansible" package should never be instlalled
anywhere by default. It's not needed, at all. ansible-core contains
all the important python modules and executable tools, except for a
very bulky and unnecessary suite of roughly 100 third party modules,
only a few of which are of use on a normal ansible sysetup and each of
which can be installed more efficientlywith the ansible galaxy
collection commands.
Stick to ansiblc-core.. There are RPMs for ansibl-core 2.12 on RHEL 8
and RHEL 9, and ansible-core 2.13 can be installed with the python38
optional installation if you feel the need. I publish RPM building
tools for ansible 6 and ansible-core 2.13 over at
https://github.com/nkadel/ansiblerepo/, if you feel the need to that
upgrade in the short term, but I don't recommend it for production use
yet. ansible-core 2.13.1 upstream relies on "pywinrm", and the
dependency chain for that is a nightmare.
Nico Kadel-Garcia
> ----------
> Brian Coca
>
> --
> You received this message because you are subscribed to the Google Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
ansible-proje...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CACVha7fMC86Ys8wvi19D%3DnZ6GVhzUeTBYLyRA5vFO19bdFC7Hg%40mail.gmail.com.