Automated publishing to the AUR #229
Open
+67
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.