[wpkg-users] [Bug 107] WPKG fails to check for equality of registry data

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=107





--- Comment #2 from Rainer Meier <r.meier at wpkg.org>  2008-04-10 19:14:59 ---
Created an attachment (id=110)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=110)
Full package, same changes for 1.1.0 pre-release (includes other fiexes too)

Here's the same update for the 1.1.0 milestone release. It includes other
changes too:

FIX: Fixed Bug 107. Registry equality checks throw an error in case of checked
     value is of type REG_DWORD or REG_BINARY. Now the values are converted to
     strings before comparing it to the 'value' attribute. REG_MULTI_SZ and
     REG_BINARY values are concatenated using newline characters. For
     REG_BINARY values each octett is converted to its decinal number
     representation. Examples:
     REG_MULTI_SZ = a
                    b
                    c
     value = "a
     b
     c"
     will match.
     REG_BINARY values will be converted to multiline string as well. Each
octett of the binary value
     is converted to its decimal representation.
     REG_BINARY = "11 22 33 44"
     value = "17
     34
     51
     68"
     will match.

MOD: Misleading/confusing info message about non-zero exit code (even if exit
     code was 0) changed from:
     Command '<cmd> returned non-zero exit code [<code>]. This exit code...
     to
     Command '<cmd>' returned exit code [<code>]. This exit code...
     The quoting has been fixed as well (see above).

MOD: Download XML nodes are now allowed as sub-nodes of any command (install/
     upgrade/downgrade/remove). This allows you to specify a download which is
     only downloaded for a specific command. This was implemented since it
     usually makes no sense to download the installation package again right
     before the remove commands are executed (which usually runs a local
     uninstall command which does not need the original installer).
     Specifying a download XML node on the global package level (not below a
     specific command definition) is still allowed. Such downloads will be
     executed regardless of the command to be executed. So you can specify some
     global downloads which are executed in any case.
     Note: If multiple install (or upgrade/downgrade/remove) commands are
     specified WPKG will download the the files of all command nodes of the
     same kind before starting to execute the commands in sequence.
     Example:
     <package...>
     <donwoad url="http://example.org/package.exe" target="package.exe" />
     <install cmd="%TEMP%\file.exe some arguments" ...>
       <donwoad url="http://example.org/file.exe" target="file.exe" />
     </install>
     <install cmd="%TEMP%\file2.exe some arguments" ...>
       <donwoad url="http://example.org/file2.exe" target="file2.exe" />
     </install>
     <upgrade cmd="%TEMP%\update.exe arguments" ...>
       <donwoad url="http://example.org/update.exe" target="update.exe" />
     </upgrade>
     </package>
     This definition will simply download "package.exe" (global). "file.exe"
     and "file2.exe" right before the install commands are executed in
     seuence.
     In case of upgrade it will download "package.exe" (global) and
     "update.exe" before executing the upgrade command(s).

NEW: Checks of type 'execute' allow to use environment variables within the
     'path' attribute now. For example the following specification is valid
     now:
     "%SystemRoot%\mycheck.cmd"


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.