[wpkg-users] [Bug 132] wpkg.js should return 3010 even when reboot is overridden

[bugzilla-daemon at bugzilla.wpkg.org]

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





--- Comment #7 from Rainer Meier <r.meier at wpkg.org>  2009-03-29 16:28:10 ---
Created an attachment (id=129)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=129)
Same changes for WPKG 1.1 testing version

Changes in this release:


MOD: Changed behavior of wpkg.js again in case reboot is overridden.
     Previously it was exiting with exit code 3010 but this caused WPKG client
     to initiate a reboot immediately after wpkg.js terminated.
     Now WPKG returns code 3010 << 8 (3010 bit-shifted by 8 bits to the left)
     which evaluates to a decimal value of 770560. This allows an external
     tool to verify if a reboot was initiated but overridden.
     If you would like WPKG to exit with code 3010 without issuing a reboot
     consider to specify a reboot command within the configuration
     (see rebootCmd in config.xml or /rebootcmd: switch) which points to a
     script which does not do anything. In this case WPKG executes the script
     (e.g. reboot.cmd) and then exits with code 3010.
     This was discussed in Bug 132.
FIX: Fixed invalid env-splitting introduced in earlier pre-release version.
FIX: Fixed environment setup for package install/remove/upgrade.
FIX: Package IDs wrongly read from profile.
FIX: Fixed recursive dependency tree build introduced in previous milestone
     checkin.
FIX: Fixed error if profile does not have any packages assigned.
NEW: Shows usage if executed without parameter (instead of just throwing an
     error and exiting).
MOD: Improved documentation.


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