Hi Lorenzo,
On Wed, Oct 30, 2013 at 11:54 AM, Rob Reynolds <r...@puppetlabs.com> wrote: > I am curious if you have also looked at the other package providers that > are out there - http://forge.puppetlabs.com/modules?q=windows+package > I can tell you that the chocolatey provider does allow ensure => latest. > Also the version on github is being improved to add source in addition to > other things and will be updated sometime in the future. > > To answer your question about the uninstall with the windows package > built-in provider, are you seeing this with all MSIs or just a specific one > (perhaps that was custom built)? MSIs should upgrade themselves, unless > there is an error in the MSI installer logic. Or if the logic allowed side > by side installs, in which case I don't think the provider takes that into > account. > I agree with Rob, it sounds like the MSI is not authored correctly. Typically, each version of an MSI for a given product should have the same UpgradeCode, so that Windows recognizes that you are installing a new version of an existing product. If on the other hand, the product can co-exist with older versions, then you'll need to treat them as independent `package` resources in your manifests. Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2Bu97um0CzDe3tpn4R1qi2OZFZ6GKW%2BXs4WcbiWnY%2Bt7WQ6t6g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
