Skip to content

Conversation

@maxtheaxe
Copy link

The error thrown when attempting a build with uninitialized git submodules is not helpful (I ran into it). This PR adds an instruction to initialize them in the README and checks within the build scripts.

_image="chromium-builder:trixie-slim"

# Fail fast: required submodule must be initialized before any Docker work
if [ ! -f "${_base_dir}/helium-chromium/utils/downloads.py" ] && [ ! -f "${_base_dir}/helium-chromium/utils/clone.py" ]; then
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should fail if ANY file is missing not only if both of them.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

additionally do not re write code just define one function in shared.sh verify_submodules and use it here.

fi

# One of these utilities must exist if the submodule is initialized
if [ ! -f "${_main_repo}/utils/downloads.py" ] && [ ! -f "${_main_repo}/utils/clone.py" ]; then
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should fail if ANY file is missing not only if both of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants