When a package deployed by ZIP-Deployment is no longer needed, it is not removed when you remove the entry from the JSON-File. This is understandable and expected.
However there is no way to tell the windev-cookbok in its JSON-Configuration file that a package (and thus the folder it should be extracted to) is to be removed. Currently I'm working around this by supplying a nearly empty ZIP (an empty ZIP generates an error, so there needs to be a file in the ZIP), but I would like to specify that the package should not be installed at all.
The most logical way would be to specify that "no version" should be installed - so setting the target version to nil will cause the entry to remove the extraction folder if it is present.
I will add this feature to the ZIP-Packaging only as I don't know if and how to specify that chef should uninstall a Windows-Installer package...
When a package deployed by ZIP-Deployment is no longer needed, it is not removed when you remove the entry from the JSON-File. This is understandable and expected.
However there is no way to tell the windev-cookbok in its JSON-Configuration file that a package (and thus the folder it should be extracted to) is to be removed. Currently I'm working around this by supplying a nearly empty ZIP (an empty ZIP generates an error, so there needs to be a file in the ZIP), but I would like to specify that the package should not be installed at all.
The most logical way would be to specify that "no version" should be installed - so setting the target version to
nilwill cause the entry to remove the extraction folder if it is present.I will add this feature to the ZIP-Packaging only as I don't know if and how to specify that chef should uninstall a Windows-Installer package...