Skip to content

Conversation

koko-ng
Copy link

@koko-ng koko-ng commented Jan 2, 2023

Hi :)
For some build systems there were calls to build before shell, which made it impossible to open a shell in the build environment if the build failed. I don't think that moving shell before has an implication on the environment as the code in between only seems to do checks on the project.

Fixes #479

@TingPing
Copy link
Member

TingPing commented Jan 3, 2023

It does change the behavior since previously it would configure the project, then open a shell, now it just opens a shell.

I'm not sure this distinction matters or not but another possibility is if run_shell is TRUE to not consider configuration failures as fatal?

@nbenitez
Copy link
Contributor

I'm not sure this distinction matters or not but another possibility is if run_shell is TRUE to not consider configuration failures as fatal?

Yes please, otherwise how am I suppose to debug a module that fails in configure step? if I'm not able to open a shell in that case..

@bbhtt
Copy link
Contributor

bbhtt commented Oct 18, 2025

This sounds like the better fix to me #625 (comment)

You opened the PR from your main branch and I can't rebase it, @koko-ng can you rebase this?

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.

[Bug]: --build-shell parameter stops after configuration not download/unpackaging

4 participants