New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix BOOTSTRAPPER_REQUEST_STATE_CACHE #4393
Comments
|
Apparently, the cache state was supposed to be between ABSENT and PRESENT. So if the package is not installed, CACHE should make the default execute=none and cache=Yes. If it is installed, all packages should behave like the MSI/MSP packages right now.
|
This should be fixed with the changes for issue 4432.
|
Still a problem for a BA.
|
|
v4.0 pull request: 99 I will wait until the v4 pull request is merged before porting back to v3.
|
v3.10 pull request: 221
|
Currently, when a BA requests
BOOTSTRAPPER_REQUEST_STATE_CACHE
the behavior depends on the package type. ExePackages and MsuPackages always convert it toBOOTSTRAPPER_ACTION_STATE_NONE
. MsiPackages and MspPackages convert it toBOOTSTRAPPER_ACTION_STATE_UNINSTALL
if they're present and uninstallable, otherwise they convert it toBOOTSTRAPPER_ACTION_STATE_NONE
.Install log:
Modify log:
The text was updated successfully, but these errors were encountered: