To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112947
                 Issue #|112947
                 Summary|NSIS ExecWait of OOo installers results in parallel in
                        |stalls
               Component|Installation
                 Version|OOo 3.2.1
                Platform|Unknown
                     URL|http://JesusnJim.com/OOo.html
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|of
             Reported by|jmichae3





------- Additional comments from jmich...@openoffice.org Mon Jul  5 20:21:46 
+0000 2010 -------
I write a wraparound NSIS installer for my OpenOffice.org Productivity Suite. 
my installer has a problem with your installer: 
I use the NSIS command ExecWait to execute your installer. on every program in
existence except OOo's pieces it does what it should: NSIS waits until the
program in question is finished installing before it goes on to the next line of
code.

OOo seems to be spawning new processes and then killing off the parent.  it used
to be I could simply do a waitjob on setup.exe until setup.exe finished, and
then I would be good to go.

but all of them (lang pack, sdk, OOo, old URE, etc) just blast straight through
and the setup has not finished, so now I have several OpenOffice.org installers
running simultaneously, and clipart installing.  a real mess and a big system
load and it's a memory hog.

please make the installers a single-process, single-tasking wonder and solve
this problem so that ExecWait on OOo or one of its parts like langpack will
truly wait until the setup for that component is truly finished.

stripped down version of my NSIS code:
SectionGroup "Office"
Section "OpenOffice.org ${OFFICE_VERSION}" Sec_ooo
    ExecWait "$EXEDIR\OOo_3.2.1_Win_x86_install-wJRE_en-US.exe" $EXIT_CODE
    ;;wait until setup.exe appears
    ;!insertmacro ExecWaitJob "setup.exe"
    ;; let's hope they never press cancel or we're in for an infinite loop!
SectionEnd

Section "OOo Language Pack ${OFFICE_VERSION}" Sec_ooolang
    ExecWait "$EXEDIR\OOo_3.2.1_Win_x86_langpack_en-US.exe"
    ;;wait until setup.exe appears
    ;!insertmacro ExecWaitJob "setup.exe"
    ;; let's hope they never press cancel or we're in for an infinite loop!
SectionEnd

Section "OpenClipart 2.0 (recommended)" Sec_openclipart
    ExecWait '$EXEDIR\clipart.exe x -y -o"$PROGRAMFILES\Open Clip Art 
Library\$\"'
SectionEnd

SectionGroup "Developer Tools/SDK's"
Section "OpenOffice.org SDK ${OFFICE_VERSION}" Sec_sdk
    ExecWait '$EXEDIR\OOo-SDK_3.2.1_Win_x86_install_en-US.exe'
    ;;wait until setup.exe appears
    ;!insertmacro ExecWaitJob "setup.exe"
    ;; let's hope they never press cancel or we're in for an infinite loop!
SectionEnd
SectionGroupEnd
SectionGroupEnd



The ExecWaitJob used to work at one time, then it didn't work anymore.  it was a
hassle, and was prone to infinite loops (hangs).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org
For additional commands, e-mail: issues-h...@installation.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to