bugzilla-daemon at bugzilla.wpkg.org schrieb: > http://bugzilla.wpkg.org/show_bug.cgi?id=149 > > > > > > --- Comment #8 from Rainer Meier <r.meier at wpkg.org> 2009-03-30 23:18:50 --- > >>> As I said a custom "execute" check can be configured already now. This check >>> could verify if the application should be applied on the system. If not, it >>> just returns exit code 0 to tell WPKG that the package is already installed. >>> > > >> Just to be clear, here you are referring to an <install> element running a >> script command and that script checking the prerequisite status, right? >> > > No. Actually here I was referring to a <check type="execute" .../> statement. > This allows the specified script to be executed and its exit value to be > evaluated. > > e.g. > <check type="execute" condition="exitcodesmallerthan" value="1" > path="%SOFTWARE%\somescript.cmd" /> > > This script might return 0 now to indicate to WPKG that it is successfully > installed so WPKG will not run any install command and assume everything is > fine. > Just to understand your statements a bit clearer: So I would use this script to determine e.g. if the disk space requirements on a machine are met. The script should return 0 if the disk space is low, so that wpkg "thinks" the package is already installed - and has the package in the local wpkg.xml - and tries to deinstall it when the package is removed from profile. Even when it isn't really installed - and the script returns 0 for "space too low" - so wpkg tries to uninstall the package on every run, since the "space too low" meens for wpkg "package is installed"?? Best regards, Falko |