Kay Ramme - Sun Germany - Hamburg wrote:
Stephan,
Stephan Bergmann wrote:
Again: If I have two instances A and B of an application installed,
and want to have a per-installation deployment variable C for that
application stored in the registry, what would the involved registry
keys have to look like for instance A to have C with value D and
instance B to have C with value E?
Good question, somehow the registry keys for A and B have to be
different. Actually I don't know, how this is conceptually solved, e.g.
what is going to happen if I install OOo two times. Probably the second
installation just overwrites the keys of the first, if so, I think we
don't need to solve something which is not solved by Windows itself.
Anyway, putting some more thoughts into this, I think the perfect
solution would be, to specify the to be used URE in the registry of the
active (the last) installation, comparable to all other registry entries
created for a particular OOo installation. The deployment parameters
than just reference the registry entries, in case someone wants to
change the URE for a particular installation he / she
* may either change the registry entry for the active installation, or
* directly the deployment parameter of a particular installation.
Yes, very good aproach. Again...for a good example of how the registry
keys should look like is to install different version of a JRE.
A caveat would be if the deployment parameters would look like the
current bootstrap parameters because the delay load hook has to use the
code the expand the variables and this can only be achieved with static
linking (otherwise you'll get circular dependencies) what would increase
the size of all DLLs.
Maybe it is possible to mix using delay load stubs and PATH environment
variable so that only OOo's bootstrap code has to be linked with "delay
load" using a stub that retrieves the URE path and sets the PATH for the
process. I don't know if this will work.-..this would require some testing.
- Hennes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
