You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2022/10/07 17:41:03 UTC

[GitHub] [buildstream] staehle commented on issue #1773: Feature: Artifact Checkout Default Behavior

staehle commented on issue #1773:
URL: https://github.com/apache/buildstream/issues/1773#issuecomment-1271870284

   Thinking more about this... Changing the base sandbox to be in "build-depends" makes more sense, because it's not really logical to claim that the x86->arm cross-compiler is a _runtime_ dependency of an aarch64 zlib.so
   
   I could pass `--build` to `bst shell`, but that argument actually does more than what your docs state.  Without it by default, it stages everything as if you're looking at the sandbox after `bst build` completes, so the artifact results of that build are also placed in the final locations.  And with `--build`, it's like it's just before `bst build` runs commands.
   
   So if the sandbox is in the "build-depends", what is the intended use-case for `bst shell` without the `--build` option?
   


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