[wpkg-users] "new" behaviour since wpkg.js version 1.3.1

[Rainer Meier]

Hi George,

On 07.08.2014 06:47, George wrote:
> In my case, I found that upgrading wpkg-gp did not work because the variables
> defined in the profile were not being properly expanded:
>
> --
> <packages>
>
>      <package id="WPKG-GP" name="WPKG-GP" revision="%version%">
>
>          <variable name="version" value="0.17" />
>          <variable name="EXE"
> value="%SOFTWARE%\WPKG-GP\Wpkg-GP-%version%_x86.exe" architecture="x86" />
>          <variable name="EXE"
> value="%SOFTWARE%\WPKG-GP\Wpkg-GP-%version%_x64.exe" architecture="x64" />
>
>          <check type="uninstall" condition="versiongreaterorequal" path="Wpkg-GP
> %version% .*" value="%version%" />
>
>          <install cmd="%EXE% /S /DisableViaLGP">
>              <exit code="3010" reboot="delayed" />
>          </install>
>
>          <upgrade cmd="%EXE% /S /DisableViaLGP">
>              <exit code="3010" reboot="delayed" />
>          </upgrade>
>
>      </package>
>
> </packages>

I found this to be an issue only in recursive variable declaration. In your 
example th package variable EXE depends on profile variables. I have uploaded an 
extended wpkg.js version 1.3.2-RC1 which includes immediate expansion of package 
variables again:

<https://sf.net/p/wpkg/code/HEAD/tree/wpkg/stable/src/main/resources/wpkg/>

Changes 2014-05-14, v1.3.2-RC1 by Rainer Meier <r.meier (at) wpkg.org>
FIX: Fixed nested environment variable expansion.
      The issue only occured if environment variables were used in other
      variable declarations.
      Thanks to George and Holger for reporting.
NEW: Added reference file comparison support for file size comparison using
      '@' prefix in value.
      Thanks to Oliver Sauder.
NEW: Added support for reference file comparison in version comparison using
      '@' prefix in value.


br,
Rainer