Specify something other than msi, installshield, nsis or inno as There’s no uniform way to to do it.įor notepad++, you can use “/S”, and it’ll auto-update the software for you. This is where Windows’ not having a real native package manager really stinks. Am IĬorrect? Is there a solution for getting the update performed? The version number is the reason for the failure to update. Iīelieve the registry key used by NPP being simply “Notepad++” without Nodes but did not update the nodes to which it had deployed 6.6.6. The source to 6.6.7 I noticed that it deployed 6.6.7 correctly to new When I first deployed this, the NPP version was 6.6.6. To: Re: windows_package for Notepad++ not updating
Thinking about how to handle this… do I check for the existence of the Notepad++ key, and if it exists and matches the old version, change the display name? That might trick Chef into seeing the version’s different and installing it.įrom: Julian C. DisplayVersion seems to be relatively consistent across installations I’ve made. So DisplayVersion and several other version keys could be used rather than the DisplayName.
“DisplayIcon”=“C:\Program Files (x86)\Notepad++\notepad++.exe” “UninstallString”=“C:\Program Files (x86)\Notepad++\uninstall.exe” There must be some way to do it, because I’m pretty sure Puppet handles this (they demoed installing and then updating Notepad++ for us anyway). Notepad++ was installed, if the registry stores that information, and I imagine you could inspect the registry to see what version of This is where Windows’ not having a real native package manager really
Registry key used by NPP being simply “Notepad++” without the version number Source to 6.6.7 I noticed that it deployed 6.6.7 correctly to new nodes butĭid not update the nodes to which it had deployed 6.6.6. I have a resource defined to install Notepad++ as follows: