Design Binary Packaging Architecture

[theory]

Design the architecture for the proposed community Packaging repository. Capabilities:

• Architecture to manage build nodes
• Webhook to listen for new releases
• Queue builds to build nodes (VM, containers, or bare metal) for *nix and Windows
• Support for building against multiple versions of Postgres, at least those still supported by the core
• Client to download source, build binaries, assemble metadata (including system-specific package and library dependencies) and bundle into a zip file
• Public key signing for the zip files
• Post results to Interactions so the binary support can be listed in the Root Registry
• Repository of zip files for download
• Mirroring (rsync?)
• Protocol for third parties to build their own packaging registries that the client can use transparently
• Binary build events to be consumed by downstream packagers

Should include:

• Packaging format (also covered by Design Packaging Automation #5)
  • RFC: Binary Distribution Format rfcs#2
• Metadata
  • RFC: Meta Spec v2 rfcs#3
• Registry
• Build worker node management
• Build queue
• Build event publishing
• Root Registry Webhook callback for new releases
• Download APIs

[theory]

RFC for the binary packaging format in pgxn/discussion#2.

[theory]

Related blog posts:

• POC: PGXN Binary Distribution Format
• POC: Distributing Trunk Binaries via OCI