http://bugzilla.wpkg.org/show_bug.cgi?id=231 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |r.meier at wpkg.org Resolution| |FIXED --- Comment #1 from Rainer Meier <r.meier at wpkg.org> --- Hi, Of course it is helpful to use extended host attribute checking for checks too. I thought about this already but it needed some more integration effort. Unfortunately the patch provided would lead to quite unexpected results in many cases. Some issues: - Nested checks are not taken into account (WPKG supports logical check grouping and nesting checks) - During install/remove WPKG needs to know the amount of checks defined in the package. Packages with 0 checks are treated in special manner. I have tried to implement it in a way that existing check-hierarchies are not broken. In addition I've updated the documentation in packages.xsd. Here is a changelog: NEW: Added extended host matching for <check /> nodes. This enables to specify checks like: <check type="uninstall" condition="exists" path="Mozilla Firefox 5.0.1 (x86 en-US)" architecture="x86" /> <check type="uninstall" condition="exists" path="Mozilla Firefox 5.0.1 (x64 en-US)" architecture="x64" /> So you can specify individual checks based on specific host matches like the host architecture, OS or other attributes. Thanks to "cleitet" for suggestion. Fixes bug 205. Would you mind testing the changes in your environment? Just download wpkg.js (version 1.2.1-RC6) from here: <http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.2/> br, Rainer -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |