[wpkg-users] [Bug 149] New: Specify prerequisites for a package

[bugzilla-daemon]

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

   Summary: Specify prerequisites for a package
   Product: WPKG
   Version: 1.0.2
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: config files
AssignedTo: man...@wpkg.org
ReportedBy: erik.langel...@silvacom.com
 QAContact: wpkg-users@lists.wpkg.org


I would like a new feature in packages.xml that would allow a package to have a
prerequisite specified so that if the prerequisite is not met, the package will
be skipped. This could be a Windows version check, or checking for software
that may have been installed by another tool (e.g. Group Policy) or manually in
order to update it.

Another related useful option would be to run different commands based on which
prerequisites are met. This would handle, for example, running different
installers for 32-bit and 64-bit Windows.

Having this feature would avoid tripling the number of packages required as we
start to migrate from Windows XP to Windows Vista 32-bit and Windows Vista
64-bit.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug.
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

Re: [wpkg-users] Updated XML Schema for Packages

[Rainer Meier]

Hi Brian,

mscdex wrote:
> Hello,
> 
> I'm not sure if I'm jumping on this too early, but I thought I'd ask.

Let's say that today I noticed that I also did some changes to packages.xsd over
the past months which I did not yet commit. However I did not verify the changes
yet and thought it's better to commit than to lose them.

So in the coming days I plan to review it. It might be slightly out of sync with
the WPKG code.
I did some larger re-structuring in wpkg.js which I committed today as well.

So you might stick with the old XSD for the moment (should still be valid for
the latest check-in). In general it's not my intention to break any backwards
compatibility unless explicitly noted within the change notes (and I did not do 
so).

Please note that the XSD files are available for the 1.1 pre-release version of
WPKG only. This version is intended to use for "tryouts" and to play around with
new features. It's not targeted for production use.


br,
Rainer
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[wpkg-users] Updated XML Schema for Packages

[mscdex]

Hello,

I'm not sure if I'm jumping on this too early, but I thought I'd ask.

I noticed that with the new version of WPKG, the schema for the packages was
updated (packages.xsd). This new packages schema seems to break quite a bit
with existing packages.xml files. One difference I found was the change in
the "depends" element. It seems it now contains a string for its content and
no attributes (package-id attribute is gone). Should the string content be
the package id? Also, somewhat related, I noticed a packageReference type
that was defined and contains a "package-id" attribute like the old
"depends", but it isn't used anywhere in any elements.

Something else too, I noticed that with the previous (rev 20) and possibly
with this new revision, both require the "type" attribute name of "check"
elements to be all uppercase, which contradicts what the WPKG documentation
shows, which has all lowercase. Changing it to uppercase solved the libxml
errors I was getting before when validating against the previous schema, but
it didn't seem to when validating against the new schema?

I'm also getting other libxml errors that the path, value, and condition
attributes of "check" elements are "not allowed."

I can post the simple packages.xml I'm using if necessary, but it _does_
validate against the previous schema (after changing the case on the type
attribute names from "type" to "TYPE" of course). I'm using the latest
xmllint and libxml for validation testing.


Brian
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

Re: [wpkg-users] [wpkg-announce] Announcement: WPKG 1.0.4 (stable)

[Tomasz Chmielewski]

Rainer Meier schrieb:

> For the moment you might download it as an attachment on Bugzilla:
> .
> 
> 
> Of course I would appreciate any feedback and bug report.

Thanks a lot!

It can be now downloaded from http://wpkg.org/Download as well.


-- 
Tomasz Chmielewski
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[wpkg-users] [wpkg-announce] Announcement: WPKG 1.0.4 (stable)

[Rainer Meier]

Hi all,

I did some enhancements/changes on the stable release of WPKG and they reached a
level where I think it should be shared as an official release. So here it 
comes...


Change notes

WPKG Version: 1.0.4
Author: : Rainer Meier 
Date: 2009-03-29
Status  : Released

Changes/fixes visible to the user:

Summary:
- Unnecessary null-reference check removed from getPackageChecks() method.
- Updated help and config.xml (grammar and consistency fixes). Fixes Bug 116.
- Returns 3010 if reboot is scheduled but overrridden. Fixes Bug 132.
- When executing non-existing command returns "-1" instead of throwing error.
- Changed exit behavior in case of overridden reboot (exits with 3010 << 8)
- Show usage when no parameter is given
- improved documentation

FIX: In case a command is executed which does not exist (WScript.Shell.exec()
 throws exception) WPKG does not immediately terminate.
FIX: In case a command is executed which does not exist (WScript.Shell.exec()
 throws exception) WPKG does not immediately terminate.
FIX: Removed unnecessary check for undefined checks in getPackageChecks()
 method. It seems that selectNodes(String) never returns null but instead
 returns empty collection.
FIX: Updated help and config.xml with grammar and consistency fixes as proposed
 by Jens Geile. Thanks Jens. Fixes Bug 116.
FIX: If a reboot is initiated but overridden WPKG was returning exit code 0.
 This behavior has been changed to return code 3010 in this case which
 allows external tools to detect that a reboot should be executed.
 Fixes Bug 132.
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.
NEW: Shows usage if executed without parameter (instead of just throwing an
 error and exiting).
MOD: Improved documentation.

For the moment you might download it as an attachment on Bugzilla:
.


Of course I would appreciate any feedback and bug report.

Please stand by for some improvements in WPKG 1.1 testing release soon.

br,
Rainer
-
Easy Software Deployment >> http://wpkg.org
___
wpkg-announce mailing list
wpkg-annou...@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-announce

-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

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

[bugzilla-daemon]

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





--- Comment #7 from Rainer Meier   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.
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

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

[bugzilla-daemon]

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


Rainer Meier  changed:

   What|Removed |Added

 Attachment #121 is|0   |1
   obsolete||




--- Comment #6 from Rainer Meier   2009-03-29 16:10:25 ---
Created an attachment (id=128)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=128)
New WPKG release with some fixes and improvements.

Changes in this release:

FIX: In case a command is executed which does not exist (WScript.Shell.exec()
 throws exception) WPKG does not immediately terminate.
FIX: In case a command is executed which does not exist (WScript.Shell.exec()
 throws exception) WPKG does not immediately terminate.
FIX: Removed unnecessary check for undefined checks in getPackageChecks()
 method. It seems that selectNodes(String) never returns null but instead
 returns empty collection.
FIX: Updated help and config.xml with grammar and consistency fixes as proposed
 by Jens Geile. Thanks Jens. Fixes Bug 116.
FIX: If a reboot is initiated but overridden WPKG was returning exit code 0.
 This behavior has been changed to return code 3010 in this case which
 allows external tools to detect that a reboot should be executed.
 Fixes Bug 132.
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.
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.
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

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

[bugzilla-daemon]

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





--- Comment #5 from Rainer Meier   2009-03-29 16:09:13 ---
OK, actually I re-implemented this change. Now WPKG behaves slightly different.
Mainly it does not exit with code 3010 any more when reboot is overridden
because this could make WPKG client to actually initiate a reboot while it
should be actually omitted.

Now WPKG exits with a special code. If you still want to exit with code 3010
this possibility still exists.

Relevant changes:
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.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug.
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users