PDAL Debian Package (unofficial)

PDAL was available as Bullseye Debian package but has been unavailable since. This project aims at re-creating the package for current Debian releases, officially or unofficially.

State of this project

• there is no Debian package build yet, and no control file for that yet
• we did a proof-of-build using Dockerfile.bookworm-PDAL-2.7.2, asserting that the upstream project can be built on Debian, and with which dependencies

Proof-of-build

Given a specific version of PDAL and a specific Debian release, there is a Dockerfile with all dependencies and build steps:

buildah bud -f Dockerfile.bookworm-PDAL-2.7.2

(You may need to run buildah login ghcr.io before, to access the base image.)

If something fails

If the Dockerfile build fails, comment out the the failing step and all lines below in the Dockerfile, rerun it, and the enter the container to debug manually:

podman run --rm -it <TAG or HASH>

If a test fails

Enter the container and rerun the failing test manually. PDAL uses googletest, so you can rerun all the tests manually on the command line, with all the options of the googletest runner are available.

E.g. if during the build you see:

106/131 Test #106: pdal_filters_shell_test ......................***Failed    0.08 sec

the failing test is pdal_filters_shell_test, so you would then execute, in the container in the work directory /PDAL/:

./build/bin/pdal_filters_shell_test

GitHub Configuration

Since this project uploads images to ghcr.io, some token is required. The current GitHub instructions are:

1. Click on your profile picture in the upper-right corner of any page.
2. Click 'Settings'.
3. In the left sidebar, click 'Developer settings'.
4. Click 'Personal access tokens'.
5. Generate a new token with write:packages and read:packages access.
6. Save this token as a secret in your repository settings and use it in your GitHub Actions workflow.

Here we save the token as a repository secret named PACKAGE_WRITE_TOKEN.