[wpkg-users] [Bug 244] New commands syntax leads to exception

Stefan Pendl stefan.pendl.71 at gmail.com
Sun Oct 16 18:43:25 CEST 2011


Rainer,

> 
> So instead of writing
> <check type="uninstall" condition="exists" path="some-prog" 
> architecture="x86"/>
> 
> you can now write:
> <check type="uninstall" condition="exists" path="some-prog">
>    <condition>
>      <check type="host" condition="architecture" value="x86" />
>    </condition>
> </check>
> 
> In both cases the uninstall check will be applied only on x86 systems.
> Well, this syntax might look over-complex but it adds more 
> flexibility and 
> allows you to use any existing check (e.g. file existence, 
> file date etc.) in 
> conditions.
> 

The new syntax allows shortening some very long lines of mine, so this is an improvement not having to scroll sideways.

I assume the following would be possible now with the new condition node.

Legacy:

<install cmd='%ComSpec% /c if /i not %COMPUTERNAME% == "AnyHost" Install.exe '/>

New:

<install cmd="Install.exe">
  <condition>
    <check type="logical" condition="not">
      <check type="host" condition="hostname" value="AnyHost"/>
    </check>
  </condition>
</install>

This seems to be a much cleaner way than burying the check inside the command, especially when the command line gets very long.

---
Stefan




More information about the wpkg-users mailing list