add new finalize.py
This splits the finalization step from the bump.py script.
Now bump.py is only responsible for creating next year's FCM, kernel
configs, and updating the build files.
The new finalize.py script moves the latest FCM (the one being finalized)
unconditionally into SYSTEM_MATRIX_DEPS so all targets, regardless of
release configuration, will incude it in their builds.
Test: ./compatibility_matrices/finalize.py && m
Test: ./build/tools/build-step-0.sh
Bug: 388532499
Change-Id: Ic1c3bf1e82f54602aee514b541a927d4b02852d2
Merged-In: Ic1c3bf1e82f54602aee514b541a927d4b02852d2
diff --git a/compatibility_matrices/bump.py b/compatibility_matrices/bump.py
index 91f58d4..6c694d3 100755
--- a/compatibility_matrices/bump.py
+++ b/compatibility_matrices/bump.py
@@ -111,14 +111,11 @@
"kernel_configs", "-a", " ".join(next_kernel_configs), android_bp
])
- # update the SYSTEM_MATRIX_DEPS variable and the phony module's
- # product_variables entry.
+ # Replace the phony module's product_variables entry to add the new FCM
+ # to the development targets (trunk* configs).
lines = []
with open(android_bp) as f:
for line in f:
- if f" \"{self.device_module_name}\",\n" in line:
- lines.append(f" \"{self.current_module_name}\",\n")
-
if f" \"{self.current_module_name}\",\n" in line:
lines.append(f" \"{self.next_module_name}\",\n")
else: