Overview
Let's check the feasibility of this task.
What I have in my mind now is,
Automate .deb packaging of circle-interpreter via GitHub Workflow
Steps in the Github Workflow
-
Build circle-interpreter binary
- Use existing build logic inside ONE to compile the
circle-interpreter binary.
-
Package into .deb format
- Manually copy the built binary into packaging root (e.g., usr/bin/) before invoking debuild.
-
Publish the .deb file
- Upload generated
.deb and its related files to Launchpad for public access.
- NOTE: Launchpad upload should be done manually, as GPG key handling within GitHub Actions is insecure.
- Maybe we can handle GPG private key in the workflow's input field, so that only one who has private key can trigger this workflow.
Originally posted by @shs-park in #14669
Overview
Let's check the feasibility of this task.
Originally posted by @shs-park in #14669