external commands: Wait for process to finish before exiting (#10100)
Issue #10063 points out that cabal exits before the external command has finished executing. This was a simple oversight to not waitForProcess on the result of calling createProcess. This also points out the flaw that there isn't a way for external commands to signal failure, so we now also propagate the exit code from the external process. Fixes #10063
Showing
- cabal-install/src/Distribution/Client/Main.hs 2 additions, 2 deletionscabal-install/src/Distribution/Client/Main.hs
- cabal-testsuite/PackageTests/ExternalCommandExitCode/cabal.out 8 additions, 0 deletions...-testsuite/PackageTests/ExternalCommandExitCode/cabal.out
- cabal-testsuite/PackageTests/ExternalCommandExitCode/cabal.project 1 addition, 0 deletions...tsuite/PackageTests/ExternalCommandExitCode/cabal.project
- cabal-testsuite/PackageTests/ExternalCommandExitCode/cabal.test.hs 38 additions, 0 deletions...tsuite/PackageTests/ExternalCommandExitCode/cabal.test.hs
- cabal-testsuite/PackageTests/ExternalCommandExitCode/setup-test/AAAA.hs 8 additions, 0 deletions...e/PackageTests/ExternalCommandExitCode/setup-test/AAAA.hs
- cabal-testsuite/PackageTests/ExternalCommandExitCode/setup-test/CHANGELOG.md 5 additions, 0 deletions...kageTests/ExternalCommandExitCode/setup-test/CHANGELOG.md
- cabal-testsuite/PackageTests/ExternalCommandExitCode/setup-test/LICENSE 30 additions, 0 deletions...e/PackageTests/ExternalCommandExitCode/setup-test/LICENSE
- cabal-testsuite/PackageTests/ExternalCommandExitCode/setup-test/setup-test.cabal 25 additions, 0 deletions...Tests/ExternalCommandExitCode/setup-test/setup-test.cabal
- changelog.d/issue-10063 14 additions, 0 deletionschangelog.d/issue-10063
- doc/external-commands.rst 2 additions, 1 deletiondoc/external-commands.rst
Loading