From 8bc73ef33c9b7a7e50578009dd945bed049ea02a Mon Sep 17 00:00:00 2001 From: "David M. Bryson" Date: Mon, 9 Sep 2024 20:27:06 -0700 Subject: [PATCH] Tritium README tweaks - Fixup image link - Disambiguate system unification from graph unification --- README.tritium.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.tritium.md b/README.tritium.md index e74fddb9..1af3d071 100644 --- a/README.tritium.md +++ b/README.tritium.md @@ -53,7 +53,7 @@ Tritium will incorporate concepts from llbuild1, llbuild2, and llbuild2fx. The * Build * Outstanding, in-progress request to produce a specific artifact from the overall build namespace -[Image: docs/tritium.jpg] +![Tritium Classes](./docs/tritium.jpg) ### Engine Components @@ -83,7 +83,7 @@ Expected Strategies * Resume-able Actions * Defined API for reconnecting/de-duplicating in-flight action computations within the executor -## Build Graph Unification +## Build System Layer Unification/Fusing The existing ecosystem of llbuild clients have well-tested, reliable implementations of build rules that cover low-level project definitions and higher level multi-project OS relationships. As much as practical, the goal is to provide an incremental path for these existing clients. Although the major benefits in expressivity come from adoption of the new API constructs, providing adapters should enable a smoother on-ramp for existing services and offer the potential for earlier interoperability.