Rainer Meier wrote: > Hi Joe, > > Joe wrote: >> Is there any way to expand variables in the debug output? > > No, this is not planned yet. However I made a note here locally that I > could identify some of the debug messages where this could be helpful. > Doing it in all debug messages has two major drawbacks: > - Some debug messages should not be expanded > - Expanding all messages is a waste of resources > > So I prefer to pick a few debug messages where the variables could > probably be printed after expanding as well (printing the variable name > and somehow its value in braces). But again, I don't want to do that for > all messages. > > br, > Rainer > Maybe expanding could be an command line option? At any rate, the reason I asked was that I had a situation where I set: set SOFTWARE=%WPKGROOT%\Programs\ Then in some packages... <install cmd='"%SOFTWARE%\thunderbird\Thunderbird Setup 2.0.0.14.exe" -ms' /> <install cmd='"%SOFTWARE%\firefox\Firefox Setup 2.0.0.14.exe" -ms' /> <install cmd='"%SOFTWARE%\PDFCreator\PDFCreator-0_9_5_setup.exe" /VERYSILENT /NORESTART /SP-' /> These somehow all installed correctly with the trailing slash on SOFTWARE. The next would not install and I could not figure out why... <install cmd='msiexec /qn /i %SOFTWARE%\OpenOffice\openofficeorg24.msi' /> I had a 1619 error but could not understand the problem since the prior three packages worked. I finally created a package to dump the environment vars to a file and then noticed my mistake. I still don't understand why it worked for the first three. |