Silent install of Netbeans 6.0 isn't always silent. If there is a problem with the install,
a window may pop up. If the window can't pop up, the installer is silent, but nothing gets
1) netbeans-6.0-cpp-solaris-sparc.sh --record state.xml
2) rm -rf netbeans-6.0
3) netbeans-6.0-cpp-solaris-sparc.sh --silent --state state.xml
4) if $DISPLAY is set:
A window pops up saying:
It seems that the installation of Base IDE is corrupted.
(this is not silent!)
if $DISPLAY is not set:
the installer exits without installing and no message that the install failed,
but at least the command returns a non-zero exit status.
I don't know if there are other error conditions that act this way, or if they would cause
problems should the install proceed, but for this particular problem, I think it would be
okay to go ahead and install silently.
yes, we do have such a problem...
Yes, there is bunch of problems when such UI warning will show.
I can`t personally say what should be the default action (exit or continue) in each case..
The most frequent are the following:
1) The installer lock file exists. This could occur in two cases :
a) another instance of the installer is running at the same moment
b) the previous running installer instance was terminated abnormally e.g. using task manager or kill command
I guess to treat such a case as a critical and exit with non-zero code. (user can always add --ignore-lock to disable
2) Installation data (~/.nbi/registry.xml) is somehow corrupted (truncated or similar).
This case I will also treat as critical and installer will exit in that case
3) User deleted installation data (~/.nbi) and then invoked the uninstaller.
In such a case uninstallation can`t proceed since there not enough information for doing that.
The default action is the same - exit.
4) Installation validation (the case you described).
I tend to think that in such a case the installation can be continued (it is not clear what to do with rear cases such
as described in Issue 111220).
If you have any objections/suggestions - pls let me know.
Hopefully fixed now in development builds.
David, feel free to add comments/questions/suggestions.