At the moment, I'm updating the surrealist-bin package on the Arch User Repository manually, but this can be automated, and ownership can be given to the SurrealDB developers.
The way the AUR package works right now is by extracting from the released .deb packages - since they're just Linux executables, running surrealist or opening it from the .desktop app works without issue.*
The build step does need to use a separate script to generate the package definition (called PKGBUILD) in ci/generate-pkgbuild.py, but this can be moved to another directory if needed. I've followed the examples from the docs of the Publish AUR Package action which is being used.
To get this working, an AUR account can be made (with a public key configured in settings) which I give co-maintainer to, and then the AUR_PRIVATE_KEY secret can be set on GitHub.
Let me know what you think 👍
*Note: If running surrealist from the CLI, an environment variable must be set for the window to display properly, WEBKIT_DISABLE_DMABUF_RENDERER=1 because of an upstream issue with webkit2gtk on Nvidia GPUs. This isn't an issue if opening from the desktop entry, as the environment variable is already set.
At the moment, I'm updating the surrealist-bin package on the Arch User Repository manually, but this can be automated, and ownership can be given to the SurrealDB developers.
The way the AUR package works right now is by extracting from the released
.debpackages - since they're just Linux executables, runningsurrealistor opening it from the.desktopapp works without issue.*I've added a step to the GitHub
push-release.yamlworkflow, which I've tested locally, end to end using act - it's working and publishing correctly if supplying it with my private SSH key in theAUR_PRIVATE_KEYsecret. Here's one change it commited: https://aur.archlinux.org/cgit/aur.git/commit/?h=surrealist-bin&id=681d6803d978f3517e06fbdae647a092d3f7d6caThe build step does need to use a separate script to generate the package definition (called PKGBUILD) in
ci/generate-pkgbuild.py, but this can be moved to another directory if needed. I've followed the examples from the docs of the Publish AUR Package action which is being used.To get this working, an AUR account can be made (with a public key configured in settings) which I give co-maintainer to, and then the
AUR_PRIVATE_KEYsecret can be set on GitHub.Let me know what you think 👍
*Note: If running
surrealistfrom the CLI, an environment variable must be set for the window to display properly,WEBKIT_DISABLE_DMABUF_RENDERER=1because of an upstream issue with webkit2gtk on Nvidia GPUs. This isn't an issue if opening from the desktop entry, as the environment variable is already set.