It's 4 months since Tristan proposed we switch to BuildStream. We
discussed it again in June and Javier suggested the next step was
enabling automated conversions.
I just sent a merge request to add a `convert` script to the
definitions.git repo, and to merge in Tristan's manual .bst conversion
It also modifies .gitlab-ci.yml so that 'master' of definitions is built
with BuildStream as well as YBD on each commit:
If you want to try out the BuildStream conversion, bear in mind the
* Build-essential stuff isn't auto-converted, the
elements/gnu-toolchain files need to be kept in sync manually
* Not all existing definitions are converted. See the `convert`
script for the list of what is converted.
* Only x86_64 is converted.
* No deployment instructions are converted.
Here is a list of the work that I think remains along the road of
switching to BuildStream completely.
1. Merge some of the Linux .morph files into a single linux.bst file,
with the platform-specific kernel config set using arch conditionals
and target board variants.
I suggest we drop some of the hardware targets we support as some of
them are totally obsolete now. The exact set that can be converted
will probably be decided by who helps out in testing the conversions;
I can do x86_64, armv8 and PPC64 but I can't promise I'll have time
to do anything else.
2. Add instructions for producing disk images from the systems;
we will need to reimplment some of our "write" and "deployment"
extensions as BuildStream elements.
3. Updating the documentation on wiki.baserock.org.
4. Having a "flag day" where we remove the Baserock definitions, and
switch formally to BuildStream.
5. Converting infrastructure systems that still use Morph/YBD to
be built and deployed with BuildStream (or something else
And at this point we can all use BuildStream to build operating systems
from scratch and the world will be a happier place for sure!
Something else that would be interesting and can be done in parallel
is fixing the `unpetrify-ref` / `track` fields we carry, and trying to
implement automated component updates. The `bst track` command makes it
fairly simple to do this.
. Episode II:
. This is the current version of 'convert':
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575
I was curious about buildstream and thought I might try it.
It's nice to see a project using man pages written the old fashioned way,
here are some portability fixes for those man pages.
If you prefer me to open this as a merge request on gitlab I could do that,
but it requires creating an account and it seems unlikely that I will need
to make further use of that account since I'm not a real contributor.
I've preserved the original layout of these man pages as much as possible,
but the indentation will look slightly different now. This patch makes
no change to the content of these man pages.
Hope this helps,
Richard Ipsum (1):
man: portability tweaks
man/bst-artifact-receive.1 | 2 +-
man/bst-checkout.1 | 2 +-
man/bst-fetch.1 | 17 ++++++----
man/bst-shell.1 | 4 +--
man/bst-show.1 | 79 ++++++++++++++++++++++++++--------------------
man/bst-source-bundle.1 | 15 +++++----
man/bst-track.1 | 15 +++++----
man/bst-workspace.1 | 36 ++++++++++++++-------
man/bst.1 | 72 ++++++++++++++++++++++++++++--------------
9 files changed, 149 insertions(+), 93 deletions(-)
I humbly submit this small patch to you.
Richard Ipsum (1):
luxio: Switch to new upstream
open-source-lorries/luxio.lorry | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)