I do not think this is possible when dealing with binary patches. This is because the binary differences are going to be specific to the base package the patch was built against. You will always have to have individual patches to "jump" over versions in this case. This is why using binary patches can be very management intensive as you either have to cover all upgrade situations, or force a specific update path (used by most companies that use this model).
Now if you were including full files in the patches, this is a completely different story. Here it does not matter what patches may already be on the system as the full file will be laid down at all times. Mat Skildum This email (including any attachments) is proprietary to Aspect Software, Inc. and may contain information that is confidential. If you have received this message in error, please do not read, copy or forward this message. Please notify the sender immediately, delete it from your system and destroy any copies. You may not further disclose or distribute this email or its attachments. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
