Hi
I'd like to fix this bug: https://sourceforge.net/p/wix/bugs/3321/
It got started in this question:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/a-patch-bundle-uninstall-doesn-t-remove-superseded-msp-patches-td7586582.html
and
I was told I could work on that myself.
The intention would be that a bundle removes the patches it has installed,
even though the patches are already superseded. Currently, the bundle
leaves them on the system and uninstalls itself, leaving zombies. That's
the case with FixPacks and superseding turned on, or all ServicePacks as I
got the impression.
But i've never done that before on a community project, so i'm a bit unsure
about the proceedings.
Also, since I've never done anything for WiX i wondered if someone could
throw me a bone and tell me if starting in burns mspengine.cpp makes sense?
I had a look at the code and ended in the
mspengine::MspEnginePlanCalculatePackage method.
There it looks like BOOTSTRAPPER_PACKAGE_STATE_SUPERSEDED just isn't
mentioned and adding that (and treating it like ..._PRESENT) would kind of
be a possible first step in the solution.
I also see the problem that this would change the behavior of the engine
and some might not like that, so I don't know if there'd be a requirement
to configure that in the xml to retain backwards compatibility?
Or if that's totally the wrong direction to go...
Cheers
Jakob
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
