Would it be well-received to create an extra artifact that generates a Slackware txz?

General
1

Hi everyone,
I’d like to propose adding Slackware package builds to Atuin’s release pipeline for a specific but useful use case.

Background: I use UnRAID, which boots from a flash drive and doesn’t persist shell history between reboots. Atuin would be perfect for this since it can store history in a database, but UnRAID uses a specific package format.

What’s needed:

  • Add a build step in .github/workflows/release.yml after the existing Linux build
  • Install makepkg on the Ubuntu runner
  • Create proper Slackware package structure with /usr/local/bin/atuin and metadata
  • Output a .txz file alongside other release assets
  • Some minor scripting to make sure atuin runs at boot and is configured in a way that persists authentication

What do you all think?

2

Hey! Thank you for the suggestion - really appreciate you offering to handle this!

Our current philosophy is to focus on building binaries for as many platforms and architectures as possible, but leave the actual packaging/bundling up to package maintainers and other third parties

In this case, I’d prefer to avoid adding a slackware stage to our CI

1 Like
3

Sure thing :slight_smile:
I understand.