BuildStream-Migration-Bot opened a new issue #16: URL: https://github.com/apache/buildstream/issues/16
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/16) In GitLab by [[Gitlab user @tristanvb]](https://gitlab.com/tristanvb) on Apr 28, 2017, 09:54 Currently in the core of BuildStream there is a BuildElement which is a specialized element for the purpose of implementing various build elements (like `autotools`, `cmake`, etc). All of these elements share the commonality of: * staging one or more sources into `/buildstream/build` * running a series of commands defined by the element's accompanied YAML configuration * collection of the artifact from `/buildstream/install` location in the sandbox This pattern should be repeated for the purpose of deployments, currently we have a quite rigid `script` element which allows staging multiple artifact dependency chains in different places and running a series of commands allowing one to use one base runtime to operate on another staged artifact & dependencies. In order to create more kinds of deployment elements we should have a more flexible base scripting element to allow this. The design of this base scripting element should take into consideration the current usage of the script element for creating a [bootable image](https://gitlab.com/BuildStream/buildstream-tests/blob/build-gnome/elements/gnome/gnome-system-image.bst) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
