[wpkg-users] Strange behaviour with recursively expanded package variables

[Stefan Pendl]

Am 06.01.2014 17:01, schrieb Dafydd Jones (techneg.it):
> Hi,
>
> I'm not sure what the expected behaviour for recursively expanded 
> package variables is but I'm seeing something strange here with my 
> Adobe Reader package.
>
> Here is a snippet from my package:
>
>  <package id="adobe-reader"
>             name="Adobe Reader"
>             revision="%PKG_VERSION%T2"
>             reboot="false"
>             priority="1">
>
>         <variable name="PKG_VERSION" 
>  value="%PKG_BASE_VERSION%.%PKG_PATCH_END%"/>
>         <variable name="PKG_BASE_VERSION" value="11.0"/>
>         <variable name="PKG_PATCH_START"  value="01"/>
>         <variable name="PKG_PATCH_END"  value="05"/>
>
You can't use a variable before it is declared.

The variable PKG_VERSION must be specified after all other variables it is using.

The sequence of declaration in your case would be:

1) PKG_BASE_VERSION
2) PKG_PATCH_START
3) PKG_PATCH_END
4) PKG_VERSION


--
Stefan P.

Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?