[wpkg-users] [Bug 139] inconsistent variable interpolation causing commands to fail

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=139





--- Comment #6 from Rainer Meier <r.meier at wpkg.org>  2009-07-05 23:58:45 ---
Thanks a lot for the example. I think I got the point now. Registry checks did
not allow variable expansion yet and this for a good reason: REG_EXPAND_SZ
strings within the registry are very common to include variables in the form of
%VAR%. Expanding variables within the check definition would make it impossible
to match a value which contains variables as it would be expanded all the time
before matching. So I've implemented a more smart algorithm now.
WPKG will now try to match the unexpanded value and just if it fails it will
try the expanded value too.

You might want to try the latest 1.1.2-RC1 pre-release:
<http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.1/wpkg.js?revision=87>


Changes:

NEW: Registry path checks can now contain variables in the form of %VAR% too.
     Variable expansion is allowed for the value attribute too. Please note
     that WPKG first tries to locate the unexpanded key and compare unexpanded
     values. For example if you use a registry equal check for the value of
     "%APPDATA%" then it first tries to look for the "%APPDATA%" string and
     only if this value does not exist it will compare the expanded value.
     This allows you to still match REG_EXPAND_SZ values which contain
     variable definitions.
     This should fix Bug 139 as reported on Bugzilla.
     Thanks to "graham" for reporting.
NEW: Variable expansion (see Bug 139) is now supported for uninstall entries as
     as well.

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.