Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix the broken --strict option to BuildPackages.sh, but only if --parallel is not also specified #4386

Merged
merged 2 commits into from
Apr 19, 2021
Merged

Fix the broken --strict option to BuildPackages.sh, but only if --parallel is not also specified #4386

merged 2 commits into from
Apr 19, 2021

Commits on Apr 14, 2021

  1. Fix BuildPackages script testing its current dir

    @wilfwilson
    wilfwilson committed Apr 14, 2021
    Configuration menu
    Copy the full SHA
    58b2c9b View commit details
    Browse the repository at this point in the history

  2. Restore some of --strict to BuildPackages script 

    gap-system#4384

The addition of the --parallel option to the bin/BuildPackages.sh
script unfortunately broke the operation of the --strict option.

This restores the functionality of --strict when --parallel is not used.

I am not 1337 enough to work out how to do catch the error codes
of parallel background processes!
    @wilfwilson
    wilfwilson committed Apr 14, 2021
    Configuration menu
    Copy the full SHA
    d16fecb View commit details
    Browse the repository at this point in the history