On Wed, 19 Apr 2017, Jordan Borean wrote:
There were plans to deprecate win_msi in the 2.3 release in favour of win_package but win_package was never hardened as a core module so it never became official. That being said win_package is the recommended of the 2 but there have been a few cases where I still favour win_msi over win_package due to the temperamental requirement over whether you need to specify a product is for some packages or not.
Yes, and for that reason I don't think we're quite ready to deprecate win_msi for v2.4.
I know we really want to, but win_package needs to be shipped with a release and working for all use-cases, before we can start deprecating win_msi IMO.
Or you risk ending up with a broken alternative, and the deprecated option people were using.
-- Dag -- 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/alpine.LRH.2.20.1705091443170.19483%40pikachu.3ti.be. For more options, visit https://groups.google.com/d/optout.
