Merge branch '21030-update-perm-cte' refs #21030

[arvados.git] / build / README

diff --git a/build/README b/build/README
index f31d39a21f8b175a52ce77339fba037086a0c827..66ca5095524665b1537e140d7f8d0c3cfd9842f0 100644 (file)
--- a/build/README
+++ b/build/README
@@ -14,13 +14,17 @@ Quickstart
 Build and test all the packages for debian10 on your architecture by
 running:
 
-    ./run-build-test-packages-one-target.sh --arch "$(arch)"
+    ./run-build-test-packages-one-target.sh
 
 This will build package build and test Docker images for debian10, build all
 packages in a build container, then test all packages in a test container.
 
 Use a different distro by adding the `--target TARGET` option.
 
+Limit the build to a single architecture by adding the `--arch ARCH`
+option. Supported architectures are amd64 and arm64. Note cross-compilation
+from amd64 to arm64 is currently only supported on Debian 11+.
+
 Limit the build to a single package by adding the `--only-build
 PACKAGE_NAME` option. This is helpful when a build is mostly in good shape
 and you're tracking down last bugs in one or two packages.
@@ -83,6 +87,8 @@ In order to build packages on a new distribution, you MUST:
 * Write `package-test-dockerfiles/TARGET/Dockerfile`.
 * Create `package-testing/test-packages-TARGET.sh`, ideally by making it a
   symlink to `FORMAT-common-test-packages.sh`.
+* Update the package download code near the bottom of `test_package_presence`
+  in `run-library.sh` so it can download packages for the new distribution.
 
 Of course, any part of our package build or test infrastructure may need to
 be updated to accommodate the process for new distributions. If you're