The reason this works poorly in practice is that the undertaking is like trying to set in stone a moving target.
packages are not named the same, the same app can appear under various names packages are not split the same way, one app can be 1 package in one distro or 3 in another packages don't stay the same inside of a distro, they get renamed, split, joined, etc, this mostly happens at distro version boundaries, but not always distros do not always have version boundaries, rolling release distros! packages with the same name are not always the same app even more fun, throw in virtual and meta packages, package groups! some distros name per language milestone python2.5-package python3.4-package others cut off at major versions py2-, py3, others at old/current py2, py- now add external/custom repos outside the tighter control of the distributions and hope that when they overlap ... it is actually what you want. now add per programming language package managers, some languages have multiple! now try to remember what my sanity looked like. This is what people really want solved, they want to say 'install apache' and have something magically navigate the above quagmire and give them what they wanted, not what they asked for. Sadly that is much more than what an ansible module was designed to do, you required a central database that is constantly updated and amended with every variation, OS, distribution and version, a 'wikipackagesmedia' which is a much larger project than I'm willing to attempt at this point in time. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJ5XC8mV1v6b4kbSm7PszqXHcsQNVOdB2sC66pebENfN2oVJmA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
