16
edits
Changes
FAQ
,Add info about precedence order for variables; statement that non-expansion in logs is intentional, not a bug
So the suggestion is clearly to use an external log rotation script if you would like to retain several log files. Personally I am perfectly fine with the default settings to just keep a log of the last execution per machine so I can see all the messages and errors produced by that machine at the moment. I am not really interested to know what happened during an installation months ago - I am just interested in the current system state - which is actually represented by the local [[wpkg.xml]] and the last execution log.
== Variables ==
=== Why aren't my variables showing up ("expanding") in my logs? ===
The issue with variables showing up "raw" in logs and other output is intentional, as stated in [http://lists.wpkg.org/pipermail/wpkg-users/2008-April/003053.html a post to the wpkg-users mailing list]. If you need to verify what a variable is expanding to, the recommended solution is to create a simple package whose install commands dump the variables to file, like this:
<install cmd="%ComSpec% /c echo Software: %SOFTWARE% > %TMP%\info.txt" />
=== What is the precedence order for variables? ===
Variable assignments have the following priority (from highest to lowest: assignments done in locations listed first will override ones listed later):
# Host XML files
# Profile XML files
# Package XML files
# The "''Variables, actions''" tab of the wpkginst.exe client utility
For example, if you assign a variable named ''foo'' in a machine profile (priority 2), it will override any existing definition in the package definition (priority 3), or on the client machine (priority 4, created by using the wpkginst.exe utility). It can, however, be overridden by an entry in the host definition (priority 1).