Skip to content

Initial implementation of automated distro package management - #24

Closed
emansom wants to merge 2 commits into
level1techs:mainfrom
emansom:feature/automated-pkg-mgmt
Closed

emansom wants to merge 2 commits into
level1techs:mainfrom
emansom:feature/automated-pkg-mgmt

Conversation

@emansom

@emansom emansom commented Mar 22, 2026 •

Copy link
Copy Markdown
Contributor

What this PR adds:

  • Uses GitHub Actions + GitHub Secrets to automatically package and bundle for PPA and AUR

  • Restructed the README.md a bit, to be more end user oriented: immediate screenshot and installation instructions.

  • PACKAGING.md as guide on how to setup the nessecary prerequisites for the automated package management within this repo

  • Corrected a syntax error in FUNDING.yml and adjusted the Level1Techs link to point to the Level1Techs Store instead.

  • Initial AGENTS.md files to provide more relevant context to Claude Code, OpenCode and other tools.

What to expect from future PRs:

  • More automated GitHub Action workflows for publishing on Fedora Copr, winget etc.

Made a shared team PPA, Launchpad+AUR account and shared G-Mail account for the package stuff.
Eventual replacement of the G-Mail with e.g. pkgteam@level1techs.com (e-mail forwarder/mailing list?) would be preferred.

See forum DMs for the KeePass file and secrets.

Replace the screenshot in README.md with one that better represents siomon capabilities after merging.

See PACKAGING.md on how to setup the workflows and secrets.

@emansom emansom changed the title Initial implementation of automated distro package management#23 Initial implementation of automated distro package management Mar 22, 2026
@emansom
emansom force-pushed the feature/automated-pkg-mgmt branch from 9e6c743 to cc47f98 Compare March 22, 2026 22:44

@eous eous left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work overall — the AUR + PPA pipeline is well-designed. The GPG keyserver retry via environment wait timers is particularly clever (zero runner cost), and the version auto-increment logic avoids manual bookkeeping. The FUNDING.yml fix and DEP-5 copyright file are solid.

See inline comments for specific issues. The changelog heredoc indentation is likely build-breaking.

Comment thread .github/workflows/publish-ppa.yml
Comment thread packaging/aur/PKGBUILD
Comment thread .github/workflows/gpg-keyserver-retry.yml
Comment thread packaging/launchpad/debian/control
Comment thread packaging/launchpad/debian/rules
Comment thread packaging/aur/PKGBUILD
Comment thread README.md
Comment thread README.md
Comment thread packaging/aur/AGENTS.md
Comment thread AGENTS.md
@eous

eous commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

Thanks for putting this together — the packaging automation is a great contribution and exactly the kind of thing that makes a project more accessible. Really appreciate the thoroughness of the PACKAGING.md guide and the clever GPG keyserver retry design.

One ask for future PRs: it'd be easier to review and merge if changes were split into smaller, focused PRs. For example, this one could have been:

  1. FUNDING.yml fix (tiny, instant merge)
  2. README restructuring
  3. AUR workflow + packaging files
  4. PPA workflow + packaging files
  5. AGENTS.md files

Smaller PRs are easier to review carefully, faster to get merged, and if something needs changes it doesn't block the rest. No stress about this one — just something to keep in mind going forward!

@emansom

emansom commented Mar 26, 2026

Copy link
Copy Markdown
Contributor Author

Smaller PRs are easier to review carefully, faster to get merged, and if something needs changes it doesn't block the rest. No stress about this one — just something to keep in mind going forward!

Yeah good call, makes it easier for git history too. Let me close this one and open some separated PRs instead!

@emansom

emansom commented Mar 26, 2026

Copy link
Copy Markdown
Contributor Author

Everything resolved in seperate PRs, re-review and merge when ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants