Feature Requests item #1827091, was opened at 2007-11-06 11:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1827091&group_id=105970
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: patching
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Heath Stewart (heaths)
Assigned to: Nobody/Anonymous (nobody)
Summary: Optionally populate MsiPatchSequence.ProductCode
Initial Comment:
One confusing issue for some people is that patch families are tied to products
and products' resources during build, but when the MSP is built patch families
belong to all products. That is, to supersede a patch another, higher-sequenced
patch must supersede all patch families previously.
Take the following example:
Patch family PFA refers to a resource in product A.
Patch family PFB refers to a resource in product B.
A single patch is created with sequence 1.0.0.1 that targets both products A
and B and contains patch families PFA and PFB.
In the future, another single patch, sequence 1.0.0.2, that should supersede
(for whatever reason; perhaps to delta patch) the previous patch is created
only for product A so it includes only patch family PFA. This new patch will
not supersede the older patch because it doesn't supersede all patch families
(i.e., PFA *and* PFB).
To change this behavior to someting that is a little more in line with how
people built the patch, pyro should optionally tie patch families to products
that contain resources referenced by any given patch family. I.e., product A
contains resources referred to in PFA so PFA is added to the MsiPatchSequence
table along with the ProductCode. If product B includes resources referenced by
both PFA and PFB, two additional entries are added to the MsiPatchSequence
table. The result looks like the following:
MsiPatchSequence
PFA, {AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA}, 1.0.0.2, 1
PFA, {BBBBBBBB-BBBB-BBBB-BBBB-BBBBBBBBBBBB}, 1.0.0.2, 1
PFB, {BBBBBBBB-BBBB-BBBB-BBBB-BBBBBBBBBBBB}, 1.0.0.2, 1
Patch families that do not belong to the listed product when the patch is
applied to a product are ignored, so when applying the patch to product B PFA,
{AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA} (the primary key is the first two
columns) is ignored.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1827091&group_id=105970
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
