Skip to content

Conversation

nbenitez
Copy link
Contributor

--build-shell is supposed to help in debbuging problems for modules, that may be a failure to build, to configure, etc.

So it doesn't make much sense that if the configuration step fails we ignore the --build-shell option, which the developer is probably using it to debug that same configure problem.

Fixes #479

--build-shell is supposed to help in debbuging problems
for modules, that may be a failure to build, to configure,
etc.

So it doesn't make much sense that if the configuration
step fails we ignore the --build-shell option, which the
developer probably use it to debug that configure problem.

Fixes flatpak#479
@nbenitez
Copy link
Contributor Author

PR #508 tried to fix this bug, but @TingPing suggested there in a comment to better use another approach which I implemented in this PR.

@@ -1590,7 +1590,7 @@ builder_module_build_helper (BuilderModule *self,
{
g_set_error (error, G_IO_ERROR, G_IO_ERROR_FAILED, "module %s: Invalid buildsystem: \"%s\"",
self->name, self->buildsystem);
return FALSE;
return run_shell ? shell (app_dir, self->name, context, source_dir, build_dir_relative, build_args, env, error) : FALSE;
Copy link
Contributor

Choose a reason for hiding this comment

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

This is passing in a non-empty error, so that won't work.

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
2 participants