This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Product registry name
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
08:24 AM
Product registry name
Hi all,
can I change the name and/or the location of InstallAnywhere's product registry '.com.zerog.registry.xml'
best regards
Kreddel
can I change the name and/or the location of InstallAnywhere's product registry '.com.zerog.registry.xml'
best regards
Kreddel
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
08:36 AM
AFAIK, no you cannot change anything about the com.zerog.registry.xml file, be that the name or the location. And it somewhat does make sense, as that registry is used by all setups that have been created by InstallAnywhere, be that yours or others... The location it might depend on the user rights, especially on Linux: if the user installing the application is not root, then a local repository will be created in the user's home directory, otherwise if it is installed as root, the registry will be created in the /var folder.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
09:06 AM
for me it would make sense, that you can give the registry an own name, because than you haven't to take care what other companies do and it is easier to maintain your own registry stuff.
On the other hand, if I have a common registry it should be easier to filter some stuff out of it, the only 'out of the box action' I have seen til now, is that you can look for a component and there the location lookup failed, if this component has no keyfile.
I think it should also give actions for analyse installed features and products.
best regards
Kreddel
On the other hand, if I have a common registry it should be easier to filter some stuff out of it, the only 'out of the box action' I have seen til now, is that you can look for a component and there the location lookup failed, if this component has no keyfile.
I think it should also give actions for analyse installed features and products.
best regards
Kreddel
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
10:18 AM
for me it would make sense, that you can give the registry an own name, because than you haven't to take care what other companies do and it is easier to maintain your own registry stuff.
On the other hand, if I have a common registry it should be easier to filter some stuff out of it, the only 'out of the box action' I have seen til now, is that you can look for a component and there the location lookup failed, if this component has no keyfile.
I think it should also give actions for analyse installed features and products.
best regards
Kreddel
On the other hand, if I have a common registry it should be easier to filter some stuff out of it, the only 'out of the box action' I have seen til now, is that you can look for a component and there the location lookup failed, if this component has no keyfile.
I think it should also give actions for analyse installed features and products.
best regards
Kreddel