2960: Merge branch 'main' into 2960-keepstore-streaming

[arvados.git] / build / README

diff --git a/build/README b/build/README
index 212e4586c41e5d15818b6aeda43487bc95322aac..e6d14cf66404009c8a6ec6f44606fb6e40f5d5d2 100644 (file)
--- a/build/README
+++ b/build/README
@@ -11,15 +11,14 @@ In order to build packages, you will need:
 Quickstart
 ==========
 
-Build and test all the packages for debian10 on your architecture by
+Build and test all the packages for a distribution on your architecture by
 running:
 
-    ./run-build-test-packages-one-target.sh
+    ./run-build-test-packages-one-target.sh --target DISTRO
 
-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.
+This will build package build and test Docker images for the named target
+distribution, build all packages in a build container, then test all
+packages in a test container.
 
 Limit the build to a single architecture by adding the `--arch ARCH`
 option. Supported architectures are amd64 and arm64. Note cross-compilation
@@ -87,6 +86,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