Greetings to the community! You might have noticed some increased traffic on the WPKG-users mailing list recently. There were quite some activities about new features and of course about fixing bugs in new and existing features. All these effort lead to a new WPKG 1.1.3-RC15 pre-release. This release passes all regression tests and is supposed to be pretty stable. Here I would like to say thank you to Stefan Pendl who spent a lot of time on testing and reporting bugs. Nevertheless I would like to announce it to the community as RC15 first and ask for feedback. If no critical bugs are found I plan to do a stable release soon after. Please find the pre-release package here: <http://wpkg.org/files/beta/WPKG-1.1.3-RC15.zip> Of course you can also just get the latest wpkg.js from SVN: <http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.1/> Recent changes (since RC11): Changes 2011-07-10, v1.1.3-RC15 by Rainer Meier <r.meier (at) wpkg.org> NEW: Added support for IA64 Itanium architecture. Basically this adds the possibility to use os="ia64" in extended host attribute matching. So the current list of supported architectures is: x86: 32-bit Windows operating system running on x86 instruction set x64: 64-bit Windows operating system running on x86-64 instruction set ia64: 64-bit Windows operating system running on IA64 instruction set Fixes bug 224. Thanks to Stefan Pendl for requesting. Changes 2011-07-09, v1.1.3-RC14 by Rainer Meier <r.meier (at) wpkg.org> FIX: Fixed minior formatting errors in usage message. Fixes bug 220. Thanks to Stefan Pendl. NEW: Printing command + expanded command in debug message when executing commands. Fixes bug 221. Thanks to Stefan Pendl. FIX: Packages which were already updated by the user (detected by precheck-update=always) were not added to the local package database. As a result such packages were checked over and over again for upgrade on each WPKG-run. Fixes bug 219. Thanks to Heiko Helmle. NEW: Supporting extended host matching in variables. Fixes bug 209. Thanks to Stefan Pendl. NEW: Added generic lcid matching for all XML elements which support extended host matching. Now the following attributes can be matched: hostname="name" os="windows 7" ipaddresses="^192\.168\.1\..*" domainname="^domain$" groups="^group.*$" architecture="x86" lcid="407,c07,1407,1007,807" These matches can be used within the following XML elements now: In hosts.xml: <host name="..." proifile-id="..." os="..." ... /> <variable name="..." value="..." os="..." ... /> In profiles.xml: <variable name="..." value="..." os="..." ... /> <package package-id="..." os="..." ... /> In packages.xml: <variable name="..." value="..." os="..." ... /> <install cmd="..." os="..." /> <upgrade cmd="..." os="..." /> <downgrade cmd="..." os="..." /> <remove cmd="..." os="..." /> Implements request filed in bug 209. Thanks to Stefan Pendl. NEW: Added host attributes to <wpkg /> node of local settings file (wpkg.xml). This allows analysis tools to get some more host information without having to parse the log files. Example node: <wpkg hostname="admin-pc" architecture="x64" os="microsoft windows 7 professional, , , 6.1.7600" ipaddresses="192.168.1.30" domainname="" groups="" lcid="807" /> Fixes bug 217. Thanks to Stefan Pendl. Update: This change did have a huge impact on test cases as wpkg-test performs 1:1 comparison to expected wpkg.xml files. As a result all checks fail. To work-around this issue unless the tests are updated I have introduced a configuration switch in config.xml: settingsHostInfo=true If set to false, then WPKG will not write host attributes to local wpkg.xml database. FIX: Extended host attribute matching uses "hostname" now for host name matching to prevent collision with name attributes in <variable /> nodes. Moreover this allows now to use classical "name=" attribute in <host /> nodes as wel as the "hostname" extended match attribute. In addition the "name=" attribute in <hosts /> have been declared as optional now. This allows to use either legacy "name" matching which does direct literal-match, IP-address match and regexp matching as well as it allows to use extended host match attributes instead. E.g. the following constructs are valid... Classial host matching: <host name="hostname" profile-id="p" /> IP-matching using classical name attribute: <host name="192.168.1.1-255" profile-id="p" /> Alternative matching using extended host attributes omitting name attribute: <host ipaddresses="192\.168\.1\..*" profile-id="p" /> Combining classical matching with extended host matching: <host name="hostname" os="windows 7" profile-id="p" /> Fixes additional bugs found in implementation for bug 209. Thanks to Stefan Pendl. FIX: Worked around a WSH issue of variable scopes in for loops. Fixes LCID handling of extended host matches. FIX: Fixed termination of processes if timeout is reached. Fixes bug 222. Thanks to Stefan Pendl. FIX: Fixed bug that "name" attribute in host node was completely ignored in previous commits. Fixes classic host-name matching. Changes 2011-07-05, v1.1.3-RC13 by Rainer Meier <r.meier (at) wpkg.org> FIX: Fixed typo while reading 'uninstalldate' attribute. Fixed many other typos mainly in comments within wpkg.js. Fixes bug 216. Thanks to Stefan Pendl for fixing. FIX: Fixed additional typos in README. Fixes bug 215. Thanks to Stefan Pendl for reviewing. Changes 2011-07-04, v1.1.3-RC12 by Rainer Meier <r.meier (at) wpkg.org> NEW: Added tabular output for the listing to report.pl script. Thanks to Stefan Pendl for providing the update. Fixes bug 213. FIX: Fixed profiles.xsd reference to example.org instead of wpkg.org. Thanks to Stefan Pendl for reporting. Fixes bug 214. FIX: Fixed typos in change log files. Thanks to Stefan Pendl for review. Fixes bug 215. Changes 2011-07-04, v1.1.3-RC12 by Rainer Meier <r.meier (at) wpkg.org> FIX: Fixed additional issue in package variable LCID matching in case variable was defined but no lcid attribute was present (which should be fully supported). Support for multiple comma-separated LCID values added. Fixes bug 206. As usually in 1.x releases wpkg.js is supposed to be 100% backwards compatible to earlier releases. So upgrading is supposed to be as easy as replacing wpkg.js and you're set to use new features. It's advised to merge the updated version of config.xml with your existing configuration - although wpkg.js should still work with your existing config.xml too. If this simple upgrade is not working for you, then please ask on the mailing list first or file a bug if you're sure the issue is not on your side. Looking forward to some feedback. br, Rainer |