Changes

* wpkg.js changes after 0.9-test3:  * new, very detailed checks (see packages.xml for more info) - thanks to Gordon Klimm * removing packages now always use "remove cmd" from packages.xml which is on the server, not wpkg.xml on the client - thanks to Gordon Klimm again

* wpkg.js changes after V 0.9-test2:test3

wpkg.js changes after 0.9-test2:* new flag: /noreboot - system will not reboot, regardless of need * /nonotify should really work now...

* wpkg.js changes after 0.9-test1:  * new flag: /nonotify - use it together with /quiet to get rid of all WPKG output / notify window.

* wpkg.js changes after 0.8:* querying packages now works fully (all /show: and /query: will work)

* querying packages now works fully (all /show: and /query: will work) Thanks to Gordon Klimm for sending patches!

* wpkg.js changes after 0.8-test2:  * small typos in wpkg.js * For a list of changes between between the stable releases, see the changelog for 0.8-test1 and 0.8-test2 (below)

* wpkg.js changes after V 0.8-test1:test2

wpkg.js changes after 0.8-test1:* small corrections in wpkg.js addressing wrong warnings in certain cases * additional comments in hosts.xml

* WPKG 0.7 (stable) released with no changes from 0.7-test1.

* wpkg.js changes after V 0.78-test1:

wpkg.js changes after 0.7-test1:* new functionality: you can execute scripts/programs once - useful for the tasks you want to do one time only, like disk defragmenting, some testing, changing printers etc.

After that, this task will be added to wpkg.xml, and will not be executed again.

* hostname case is now ignored, you can use upper and lower case and it will work * WPKG will now tell you if the syntax of XML files is not correct (which line, etc.) * new flags: /debug or /verbose - print everything WPKG does, useful for packet installation debugging (and for new users which need to understand how WPKG works)  /dryrun - "simulates" packet installing, without installing anything

* wpkg.js changes after 0.6:* regular expression support in hosts.xml!You can view the exact syntax on this page:[http://msdn.microsoft.com/library/default.asp?url=/library/en-us/jscript7/html/jsjsgrpregexpsyntax.asp http://msdn.microsoft.com/library/default.asp?url=/library/en-us/jscript7/html/jsjsgrpregexpsyntax.asp]

httpworks for://msdn.microsoft.com/library/default.asp?url=/library/en-us/jscript7/html/jsjsgrpregexpsyntax.aspb1, b10, b100does not work for: bubu, b, x, x1, x10, x100

<host name="b[0-9].+" profile-id="profile" />

works for: b1*all* hosts - use with care (!), b10, b100 does not work for: bubu, b, x, x1, x10, x100place at the bottom of hosts.xml

<host name="b.+" profile-id="profileprofile1" />

works for *all* hosts - use with care (!)"b10", place at the bottom of hosts"b11", "b12345" etc.xml

<host name="b.+" profile-id="profile2" /> <host name="bronek1" profile-id="profile1" /> <host name="bron.+" profile-id="profile3" />

works for Normally, hosts are parsed from top to the bottom, except when the hostname is not a regular expression.So host "b10bronek", will match "b11profile1", even though it also matches "b.+" and "b12345bron.+" etc(which are regular expressions).

Normally, hosts are parsed from top /force - Uses force when performing actions (ignores wpkg.xml).<br>Handy when you're not sure if your system is "up to date" with the bottomstate described in hosts.xml, packages.xml and profiles.xml (i.e., except when the hostname is not a regular expressionsomeone was adding / removing software by other means than WPKG).<br> So host "bronek" It will match "profile1scan", even though it also matches "byour system for all possible packages from packages.+" xml, and "bronthen, install and/or uninstall packages, according to profiles.+" (which are regular expressions)xml / packages.xml / hosts.xml for a given host.

  * new flags:  /force - Uses force when performing actions (ignores wpkg.xml). Handy when you're not sure if your system is "up to date" with the state described in hosts.xml, packages.xml and profiles.xml (i.e., when someone was adding / removing software by other means than WPKG). It will "scan" your system for all possible packages from packages.xml, and then, install and/or uninstall packages, according to profiles.xml / packages.xml / hosts.xml for a given host.  /forceInstall - Forces installation over existing packages.<br> The "install" command will be run, even if "check" conditions are met. This can be useful to "repair" packages etc.

* wpkg.js changes after 0.6-test1:  * More examples in packages.xml on how to use new features

* wpkgV 0.js changes:6-test1

wpkg.js changes:* Added new check type - it checks if the program is in "Software Add/Remove"

An example entry looks like below:

In the path="" field you just have to add a name which is in Windows Software Add/Remove - and that's it: you no longer have to figure out the registry entries and/or files!

Of course you can still use "file" and "registry" check types, combine them all etc. (all of them have to be met to consider software installed; they will be checked also *after* installation due to the fact that some installers don't handle exit codes properly).

* Output during the installing looks like below:

This can mean: - the installation was unsuccessful (and the package won't be written to %SYSTEM32%\wpkg.xml) because the file check condition was not met, - file check condition has a typo in packages.xml, - you don't have to use that many conditions - one "uninstall" check is often enough.

  * Changed double quotations to single quotations in packages.xml. Some installation instruction may require using double quotations.

* Download WPKG-HTTP here(see the [[Download|download]] link. * Extract it somewhere to you web server tree (for example, /var/www/html/wpkg/). * Set the document root of your Apache web server to /var/www/html/wpkg/. Alternatively, you can set the document root of your virtual host to /var/www/html/wpkg/

* Some directories under wpkg/ should be writable by your Apache server, so don't forget to

* If you have any problems, please report it to the mailing list.

* wpkg.js changes:  - * Fixed registry checking. - * If there is no '<check type="...' entry for a given package, '<install cmd="...' will be executed each time the machine is booted. This is useful when one wants to execute certain scripts on each machine startup. - * If there is more than one '<check type="...' (that is, "file" and "registry"), both of them have to be met to assume the package is installed (before it was OR - so it was any of them). - * Added checking *after* installation, too. Some installers return exit code 0 (for example, SAS 9.1.3), even though the installation was unsuccessful. This prevents WPKG from writing such package to wpkg.xml in case it wasn't really installed.  * other changes:  - we have our own domain - wpkg.org :) - the documentation - which is now on http://wpkg.org - has been greatly improved since the last WPKG release (most of you probably noticed that long time ago) - some work has been done on a web interface to WPKG