gtristan commented on issue #422: URL: https://github.com/apache/buildstream/issues/422#issuecomment-2701291953
> Hi everyone, is there any update on this? I think this could be very helpful in many situations, for instance I might want to tweak a [kernel configuration in freedesktop-sdk](https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/blob/459feb0385a3e722f56e573fc0b2e28e233e04ee/elements/components/linux.bst) inside a shell with the build tree, but ncurses or other dev-dependencies are missing in the shell. IIUC in this issue the discussion is about proposing both a way to specify project-wise shell dependencies and a way to specify additional shell-dependencies in .bst elements. I think both would be very useful. I think the initial feature is to allow the functionality first via the CLI, for both build shells and runtime shells. The main initial push for this feature is two fold: * to allow things like debugging to occur with existing built artifacts, without needing to define specific elements and build again in order to bring your debugging tools to life the shell * general IDE enablement, we had some DX folks at the time thinking hard about what will be necessary to create a great DX with buildstream I'd say that any implementation around this will be welcome so long as it is a general implementation that does not stand in the way of these goals. Project configurations for specifying shell dependencies on a project wide or element wide basis, sounds like sugar on the cake, something simple to add (most complicated part is settling on a sensible API) after having the initial CLI functionality settled. I don't expect you would get any pushback on patches towards this :) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
