[wpkg-users] [Bug 102] registry checks fail if the value name contains backslashes

[bugzilla-daemon at bugzilla.wpkg.org]

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


Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |LATER




--- Comment #3 from Rainer Meier <r.meier at wpkg.org>  2008-04-02 23:12:43 ---
This seems to be a very tricky issue. There are some workarounds described by
using some low-level API calls instead of RegRead. In fact I prefer using the
default RegRead method for portability reasons. Unfortunately there seems to be
no way to somehow encode the RegRead parameter in order to tell RegRead which
parts are actually meant to identify the value.
Using low-level API calls is currently not an option as well since this would
require to split up the registry path into two attributes (which is currently
only one within the XML definition).

On the other side there are some workarounds which could be possible. An
install script could check for the value after installation and write a file if
check succeeds. The package itself could then check for the file existence.
I know this means that it is not possible to check the registry value each time
at boot. For this there might be a package with execute="always" flag which is
executing a script which checks the value and if it does not exist re-installs
the application and in case it exists just does nothing.

I know these workarounds might not be very satisfying. I think about to
implement a check type which allows you to invoke a script. This script could
then do any kind of checks (including 'reg query...' invocation).

Due to the complexity and required changes (even enhancements) I am setting
this report to "LATER" since it will not be fixed for 1.0 release. We might
consider the changes I outlined above for the upcoming 1.1 release.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.