[GitHub] [buildstream] gtristan commented on pull request #1576: _sandboxbwrap.py: try to support architectures that don't match host

[GitBox <gi...@apache.org>]

gtristan commented on pull request #1576:
URL: https://github.com/apache/buildstream/pull/1576#issuecomment-1044121874


   I was first concerned with the additional optional dependency appearing like an API surface of sorts, i.e. "If you run BuildStream in an environment with a binary called `arch-test`, then it will be consulted for yada yada", but given that we already use `linux32` this seems to be less of a concern.
   
   That said, by applying this patch, are we setting up our users with unrealistic expectations when transitioning to BuildStream 2 ?
   
   Native building of foreign binary formats is not supported by BuildStream as far as I'm aware, and hopefully, eventually remote execution clusters could be used for that kind of thing.
   
   If we move ahead with this, we should not have the expectation that `buildbox-run` is going to behave in the same way.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org