I can totally see that line of thinking but LAYOUT is actually an outlier, just
like HELP. Honestly, if I could do it again, I wouldn’t add LAYOUT to the
command-line either and make it more like what I imagined CACHE to be.
So, ignore LAYOUT then the states a package can move through from “less to more
present” on a machine are:
UNINSTALL
CACHE
INSTALL
MODIFY
REPAIR
UPDATE (i.e. move to a newer version)
CACHE was missing. I thought it was always there. Ooops.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Heath Stewart [mailto:hea...@outlook.com]
Sent: Tuesday, March 3, 2015 9:45 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] BOOTSTRAPPER_ACTION_CACHE
Sean and Rob, during triage you mentioned that you didn't think CACHE should be
before UNINSTALL, but it was placed between LAYOUT and UNINSTALL (synonymous
with Absent often times), which logically makes sense. If LAYOUT ~= source
layout and ABSENT ~= not installed, then CACHE ~= in between source and install
- exactly what the cache is for.
So do you really think this needs to change? At the very least, it should be
close to LAYOUT which is also before UNINSTALL.
- Heath from my Surface Pro 3
------------------------------------------------------------------------------
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-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
